Integrated weather graphical user interface

ABSTRACT

Data integration and distribution systems. A system includes a graphical user interface (GUI). Weather and market data are collected. A weather symbology including symbol elements linked to segments of the collected weather data and rules for generating weather symbology instructions are stored. The GUI is generated for display on a user device. A weather symbology instruction is determined based on at least one requested symbol element indicated in a weather data request and the rules. A weather forecast dataset is created from among the collected weather data based on the weather symbology instruction. A presentation package comprising the weather forecast dataset and the collected market data is generated such that the weather forecast dataset is integrated with the collected market data. The presentation package is presented on the GUI and updated concurrent with changes at least one of the weather data, the market data and user input.

TECHNICAL FIELD

The present disclosure generally relates to improving data structuredistribution and, in particular to distribution systems, interactivegraphical user interfaces (GUIs) and methods for the integration ofdisparate data structures for interaction, including real-timeintegration of weather and market data structures.

BACKGROUND

Problems exist in the field of digital distribution platforms. Ingeneral, a digital distribution platform may manage digital data content(e.g., digital goods, digital information, etc.) and distribute thecontent to various end-users. Conventional platforms may distributedigital data content from one or more data sources (e.g., data feeds,data files, user input and the like) that may be distributed across oneor more networks, may include different data types, different dataformats, different data communication requirements, different networksecurity, different availability time periods and the like. Moreover,distribution platform may distribute data content in one or moredistribution formats (e.g., in a data file, on a user interface, in aspreadsheet and the like), to particular end-users with varying amountsof data and/or personalized data and the like. Conventional platformsalso exist that may provide the ability for user-interaction with thedistributed data (e.g., data analysis tools, actions that may beperformed with the data and the like) in addition to the presentation ofdistributed digital data content.

All of the above variables associated with data distribution make ittechnically difficult to manage data distribution and interaction forreal-time distribution. Yet further, distribution of digital datacontent in real-time becomes increasingly difficult as the volume ofdigital data content to be distributed increases and/or as the digitaldata content changes more rapidly over time (e.g., with increasingvolatility of the data content). For example, it may become increasinglytechnically difficult for a distribution platform to continually updatean interactive user interface with the most up-to-date data content,when the data volume increases and/or the data content itself changesrapidly. In such instances, any transmission delays over one or morenetworks to obtain the data content coupled with any data handlingdelays by the distribution platform for handling the received datacontent (e.g., to convert a data format of received data content, tonormalize any data content, to remove any data content not suitable forpresentation, to generate data for distribution in one or moredistribution formats, create aggregated output data, generate any userinterfaces and the like) may introduce significant errors in distributeddata and the ability by the end-user to interact with the distributedcontent. For example, the distributed data content may not provide themost up-to-date information, leading to a situation in which a user mayperform an action based on stale information (e.g., an auction for anobject at a price that no longer exists, respond to older data contentwhen newer content exists, etc.).

Another significant technical problem that still exists in datadistribution platforms includes the integration of data content fordistribution that includes disparate data types. For example, while itmay be possible to simply display disparate data types on user interfaceside-by-side, it may be difficult to integrate disparate data types inan intelligent manner, e.g., where the integration of the disparate datatypes provides meaningful information about the combination of disparatedata types. For example, a first data type may include data values thatare based on one set of underlying index values whereas a second(different and independent) data type may be based on a completelydifferent and unrelated set of underlying index values. Thus, it may betechnically difficult to suitably align and integrate disparate datatypes. It may be still more difficult to integrate disparate data typeswith real-time, rapidly changing data.

Accordingly, there is a need for a system (including a novel interactiveGUI), and method for integrating and distributing disparate data typesin a fully-automated (or near fully-automated) manner. All of this,without significant increases to the computational burden, cost, systemcomplexity, re-programming requirements and system maintenance.

SUMMARY

Aspects of the present disclosure relate to data integration anddistribution systems, methods and non-transitory computer readablemedium. A system includes one or more weather data source systems, oneor more market data source systems, at least one user device associatedwith at least one user and a data distribution system. The datadistribution system is in communication with the one or more weatherdata source systems, the one or more market data source systems and theat least one user device via at least one network. The data distributionsystem includes an interactive graphical user interface (GUI) forinteractively presenting integrated weather and market data. The datadistribution system is configured to collect weather data among the oneor more weather data source systems and collect market data among theone or more market data source systems. The data distribution system isalso configured to store, in at least one database, one or more symbolelements linked to segments of the collected weather data and one ormore pre-defined rules for generating weather symbology instructionshaving a pre-defined instruction structure. The data distribution systemis further configured to generate the interactive GUI for display on theat least one user device, receive a weather data request from the atleast one user device via the interactive GUI and determine a weathersymbology instruction based on at least one requested symbol elementindicated in the received weather data request and in accordance withthe one or more pre-defined rules. The data distribution system isfurther configured to create at least one weather forecast dataset fromamong the collected weather data based on the weather symbologyinstruction, generate a presentation package comprising the weatherforecast dataset and a portion of the collected market data such thatthe weather forecast dataset is integrated with said portion of thecollected market data, present the presentation package on theinteractive GUI and update the presentation package on the interactiveGUI concurrent with changes to one or more of the weather data, themarket data and user input via the at least one user device.

Aspects of the present disclosure also relate to data integration anddistribution systems, methods and non-transitory computer readablemedium. A system includes one or more weather data source systemsconfigured to generate one or more weather data streams, one or moremarket data source systems configured to generate one or more marketdata streams and a data distribution system in communication with theone or more weather data source systems and the one or more market datasource systems via at least one network. The data distribution system isconfigured to store, in at least one database, a weather symbologycomprising one or more pre-defined symbol elements linked to one or moresegments of the one or more weather data streams, receive the one ormore weather data streams among the one or more weather data sourcesystems via at least one data feed and receive the one or more marketdata streams among the one or more market data source systems via the atleast one data feed. The data distribution system is also configured tosegment the received one or more weather data streams based on the oneor more pre-defined symbol elements to form at least one segmentedweather data stream, receive a weather data request from at least oneuser device via the at least one network, identify at least one symbolelement among the one or pre-defined symbol elements indicated in thereceived weather data request, extract one or more segments of at leastone segmented weather data stream based on the at least one identifiedsymbol element to form at least one extracted weather stream, create areal-time weather dataset from the at least one extracted weather streambased on the weather data request and generate an integratedpresentation package comprising the real-time weather forecast datasetand the received one or more market data streams. The data distributionsystem is further configured to at least one of expose the integratedpresentation package to at least one application programming interface(API) and present the presentation package on a display of the at leastone user device, and update the integrated presentation packageconcurrent with changes to one or more of the one or more weather datastreams and the one or more market data.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a functional block diagram of an example data distributionenvironment, according to an aspect of the present disclosure.

FIG. 2 is a functional block diagram of an example weather integrationserver, according to an aspect of the present disclosure.

FIG. 3A is a flowchart diagram of an example method of generatingintegrated weather and market data, according to an aspect of thepresent disclosure.

FIG. 3B is a flowchart diagram of an example method of generatingintegrated weather and market data for streaming data, according toanother aspect of the present disclosure.

FIG. 3C is a hierarchical diagram illustrating an example weathersymbology and use of the weather symbology to form various presentationpackages, according to an aspect of the present disclosure.

FIG. 4A is screenshot including a chart of example weather forecast dataand price data as a function of exchange time, according to an aspect ofthe present disclosure.

FIGS. 4B and 4C are screenshots of an example 16 day weather forecastfor a particular location as a function of exchange time with respect tonatural gas price data, according to an aspect of the presentdisclosure.

FIG. 4D is a screenshot of an example weather alpha workflow chart as afunction of exchange time, according to an aspect of the presentdisclosure.

FIG. 5 is a screenshot including an example guidance chart associatedwith a guidance weather perspective, the guidance chart illustratingweather forecast data as a function of a forward time period, accordingto an aspect of the present disclosure.

FIG. 6A is a screenshot including an example progression chartassociated with a progression weather perspective, according to anaspect of the present disclosure.

FIG. 6B is a screenshot of an example progression chart illustratingnatural gas storage estimates and weather model progression as afunction of forecast date, according to an aspect of the presentdisclosure.

FIG. 6C is an example progression chart for several weather models as afunction of forecast date, according to an aspect of the presentdisclosure.

FIG. 7A is an example initiation screen for generating an accuracychart, according to an aspect of the present disclosure.

FIG. 7B is an example accuracy chart associated with an accuracy weatherperspective, according to an aspect of the present disclosure.

FIG. 8A is an example user interface illustrating examples of symbologyconstruction, according to an aspect of the present disclosure.

FIG. 8B is an example user interface illustrating examples of variousweather symbology structures, according to an aspect of the presentdisclosure.

FIGS. 9A, 9B, 9C, 9D, 9E, 9F, 9G and 9H are screenshots of an exampleinteractive GUI for providing interactive tools for viewing andinteracting with integrated weather and market data, according to anaspect of the present disclosure.

FIGS. 10A, 10B, 10C, 10D, 10E, 10F, 10G, 10H, 10I, 10J and 10K arescreenshots of an example interactive GUI for providing interactivetools for viewing and interacting with integrated weather and marketdata, according to another aspect of the present disclosure.

FIG. 11 is a functional block diagram of an example computer systemaccording to an aspect of the present disclosure.

DETAILED DESCRIPTION

As discussed above, problems exist in the integration and distributionof disparate data types, including in a fully-automated (or nearfully-automated) manner. One such combination of disparate data typesinvolves weather data and market data. Each of these disparate datatypes may include historical data values, current (e.g., streaming/live)data values and future (e.g., forecast) data values. Each of thesedisparate data types also rely on underlying data and information thatmay be rapidly changing. Yet further, each of these disparate data typesinvolve large volumes of data. For example, market data typicallyinvolves tens, if not hundreds, of thousands of live indicationsavailable to display at any given time, and where changes to market datamay occur hundreds, if not thousands of times in a second. Similarly,weather data may involve continually changing weather observations fromamong a large number of locations (e.g., on a global scale, on acountry-level scale, on a state-level scale, etc.), as well as weatherforecast model data that may include a number of different models, andwhich models may be updated at different update intervals. All of theabove variables make it technically difficult to manage datadistribution and interaction for real-time distribution. Because weatherand market data are also disparate data types, it becomes still furthertechnically difficult to integrate both data types in an intelligent andmeaningful manner in an interactive display, to provide insights intoboth data types (e.g., any correlations, predictive effects of one datatype on the other data type and the like). Market data, such as marketprice data may be accessed in watchlists, data tables, data grids,spreadsheets (e.g., Microsoft® Excel® via (real time data (RTD) linksembedded into Excel), as well as interactive charts. These are basicfunctions of many conventional trading desktops (e.g., trading desktopsprovided by Bloomberg™, Refinitiv™ (e.g., Eikon™), Global View, DTNExchange® and others) within the electronic financial trading community.These trading desktops were born in the 1980's and continue to evolveinto highly specialized tools, designed to instantly display market data(using a time series server based technology) which was optimized fordata delivery speed for viewing and interacting with market price data.Some conventional systems support plotting real-time market prices inreal-time with updating charting tools.

Weather data has also experienced a similar evolution. Conventionalinteractions with weather data has been primarily using weather maps,considering it was the most efficient manner to view large amounts ofdata using a single image. Over the years, processing became morepowerful and bandwidth became more plentiful, and both processing andbandwidth have become more affordable. The weather forecast modelsthemselves became significantly larger in file size and the speed toprocess these larger weather forecast files, into maps, for internetbased delivery (as opposed to fax) became the focus. At the same time,the increased computational power also allowed for the extraction of rawweather forecast ‘data’ from these computer-based files, could quicklyconvert the forecast files (e.g., in a native file format such asgridded binary format (GRIB) files) and deliver city or zip code basedweather forecasts in a few minutes. From this raw ‘data’, the creationof timely weather forecast charting tools to display a specific city'sweather forecast, over the next few days, became popular, for example,on webpages and eventually cellphones.

The present disclosure is the first to combine these two existingcharting capabilities into a unique weather charting and analysis toolthat integrates both weather and market data (i.e., disparate datatypes), including in some examples both streaming weather data andstreaming market data. In some examples, time series server basedtechnology inside a trading desktop may be leveraged and used touniquely create a one of a kind weather “weather symbology.” Thespecialized symbology allows weather forecasts to be plotted “inexchange time”, meaning the specific time when that weather forecast“element” was made available into the public domain (e.g., a forecastedtemperature, wind, humidity, etc. and/or a value-added calculation whichmay convert forecasted temperature into a value representing forecastednatural gas consumption called a Gas Weighted Degree Day (GWDD), etc.)as opposed to an “Interval start” time which displays the same forecast“element” (e.g., a predetermined number of days, such as 16 daysforward). Importantly, the system of the present disclosure may containpre-defined information in the symbology such as a weather model name,weather location, a “Forecast Valid Date (or Forecast Valid Day), Timeof Day” and model hour in the future. The unique capability created bythe present disclosure and offered inside a trading desktop of thepresent disclosure is the ability to instantly and easily visualize“Weather Alpha”, which is the weather's financial impact on varioustraded market prices. For example, if a weather forecast for say“Forecast Valid Day 9” was significantly colder than the previousweather forecast and was released into the public domain at 10:31:12 am,which that streaming information (in some examples) then caused theprice of Natural Gas, traded on an electronic Exchange, to move 5 centsin the following 10 seconds (after the release of this weathernews/forecast data), users of a trading desktop of the presentdisclosure (also referred to herein as ICE Connect or ICE Connect'sTrading Desktop) would have valuable insight over weather users, whosimply review weather maps, or interact with weather data via somedisparate source, which is not integrated with electronically tradedmarket prices.

While this process of matching the “exchange time” (aka data receipttimes) of both weather forecast data and market price data may appearsimple on the surface, there are many complexities. The problems arisebecause conventional trading desktops were originally designed to handleprices for stocks, which involves plotting the market price with an“exchange time” (aka receipt time). Futures and forward contracts weresubsequently incorporated and specialty views were created toaccommodate an instrument which has a current market price in “exchangetime” (aka receipt time) but also represents some point in the future.So a new symbol structure was created to represent these futures/forwardcontracts which represent future times the traded contract will expire,(such as a January natural gas contract, February, natural gas, etc.).These monthly futures contracts can also be stitched together to see a“forward curve” view (e.g., the January contract+Februarycontract+March+ etc.) and all those individual market prices may beupdated in real-time respectively.

The present disclosure handles weather data in a similar manner; inwhich a 16 day weather forecast (for example) is formed similar to a“forward curve.” Each weather forecast may be stitched together (as itupdates multiple times per day) thus creating a “forward curve” of a“forward curve.” In some examples, the present disclosure allows usersto interact with this weather data in one or more (e.g., three) primaryuser-weather perspective(s) to help organize the potentially multipleaspects of time related to the (e.g., streaming) data). The weatherperspective(s) represent a type of (software) workflow that may provideaccess (e.g., visualization, observation and/or interaction tools) toweather data from different perspectives (e.g., slices of a database ofweather data), thereby enhancing the symbology structure and respectiveuser-experience. In some aspects, the present disclosure may create aparticular weather symbology to provide weathervisualization/observation/interaction tools including one or moreweather perspectives (e.g., three), and a weather alpha workflow thatcombines weather and market data. Significantly, such a weather alphaworkflow has not been accomplished prior to the present disclosure.Advantages of the present disclosure include an integrated presentationpackage (including in some examples one or more weather forecast charts,tables, grids (e.g. where a user may select a particular area of thegrid and a predetermined (e.g., streaming) view of weather and marketdata may be generated responsive to the selection), etc. integrated(e.g., overlaid) with market data). In some examples, the weatherperspectives may be configured to provide more efficient access toweather data in an optimal manner, resulting in user interfaces thatquickly render any suitable chart, table, analytic value extremely fastusing static, periodic, aperiodic and/or streaming data.

In some examples, aspects of the present disclosure relate to weatherintegration systems and interactive GUIs that improve streaming weatherdata in an efficient manner into an electronic trading desktop (as wellas other client applications). Weather integration systems of thepresent disclosure are unique in that the functionality of streamingweather forecast data into a trading desktop and combining (integrating)the weather data with streaming market data (e.g., streaming price data)to create actionable knowledge does not exist outside of the presentdisclosure. The weather integration system is able to provide morecredible weather forecast models that may be made available from agreater number of weather data sources. The weather integration systemmay also provide forecasts that extend farther out in time and may beconfigured to update the weather forecast data with higher temporal andspatial resolution creating larger and larger file sizes, It isunderstood that the ability to handle and process an ever growing amountof data is a technical problem, thus the ability to handle and processstreaming raw data, and convert this streaming data into actionableknowledge via an interactive GUI (as performed by the systems of thepresent disclosure) represent a technical solution to a technicalproblem.

In some examples, weather integration systems and interactive GUIs ofthe present disclosure provides a unique technique of integrating datain an exchange time to line up changing perceptions of weather forecastmodel(s) with changes in market prices. The weather integration systemcreates a unique weather symbology that is optimally designed to blendwith other data streams which are configured to operate within a timeseries server. In general, the weather symbology may be configured forboth weather data streams and non-weather (e.g., market data) datastreams. The weather integration system of the present disclosure may beconfigured to provide access to raw data via optimally arrangeddataset(s) in a manner that may be helpful for indicating an impact ofweather data on market data, such as providing user interfaces forback-testing changing market prices as they are associated with changingweather perspectives. In some examples weather data (e.g., streamingand/or static data) may utilize the novel symbology of the presentdisclosure, which allows weather data (live and/or historical data) toflow seamlessly through a trading desktop (e.g., for interactivepresentation on a GUI), as well as for providing weather data toexternal systems (e.g., for further analysis, visualization, etc.). Thesymbology of the present disclosure is unique in that it employs thesmallest possible building blocks to organize weather data in nearly anypossible (user-customizable) manner. The highly granular symbology ofthe present disclosure allows users of a trading desktop to reviewweather data in a manner similar to market price data as well as combineany element of weather with any granular element of market price data.

The weather integration systems and interactive GUIs of the presentdisclosure provide users with unique advantages, including indicatingprecisely how changing weather perspectives may directly influencemarket prices. The weather integration system may provide variousweather maps, various weather data and various value-analytics.

The weather maps may include, in some examples, weather maps as part ofa robust weather maps application which may stream thousands of maps foreach forecast hour from various government entity weather models beingreleased into the public domain. The weather maps provided by theweather integration system may be provided very rapidly, and mayconfigured to provide comprehensive information in a manner that is easyto use (e.g., user-friendly). Weather data provided by the weatherintegration system may be provided quickly and in a manner to be easilyassessable. In some examples, the weather data may include, withoutbeing limited to, one or more of a forecast confidence (risk), aforecast volatility, a forecast accuracy; a forecast alpha and a richhistory of historical forecasts and/or observations. The weatherintegration system may provide value-added analytics be configured toinstantly convert weather data into accurate and actionable knowledge,tailored specifically for traded instruments, including, in anon-limiting example, to one or more of Gas Weighted Degree Day (GWDD),Electricity Weighted Degree Day, Propane Weighted Degree Day, HeatingOil Weighted Degree Day and the like.

In some examples, the weather integration system of the presentdisclosure may be configured to convert extremely large streams ofweather and price data into actionable knowledge, including in a mannerthat is faster than conventional systems, and provides improvedtechnical features including improved data speed, reliability,comprehensive data, a unique weather symbology that does not existoutside of the present disclosure and unique transformative weatherworkflows.

In some examples, the weather integration system may be configured toprovide a data speed to ingest, process and deliver global governmentweather forecast (e.g., raw) data, to users, in both data and mapformats with low latency. In some examples, the weather integrationsystem may be provide improved reliability of weather data, includingthe ability to acquire, render and transmit (raw) weather data in a lowlatency fashion into various types of weather delivery mechanisms. Insome examples, the weather integration system may provide comprehensiveweather data, by using high (including highest) resolution data andaccurate (including most accurate) data versions, of the most criticalglobal weather forecast models (which few (if any) other weatherproviders currently offer), as well as an enhanced temporal and spatialresolution.

In some examples, the weather integration system may provide a uniqueweather symbology having unique symbol elements (also referred to hereinas “Weather Legos”). The Weather Legos may be configured to breakdownstreaming weather data into the smallest possible building blocks topower a time series server-based trading desktop, allowing users toinstantly and easily interact with both weather and price data (e.g.,through time & space). In some examples, “Weather Legos” allow users tocreate any weather display imaginable, or easily replicate a favoritedisplay from another source. In some examples, the weather integrationsystem may provide transformative weather workflows, which workflows mayprovide an improved speed of understanding the impact of weatherincluding on market data. The workflows may leverage the “Weather Legos”and improved data speed, together with the full power of an electronictrading desktop, to create unique displays that allow users to morequickly and more precisely understand how changes in perceived weathermay directly influence market prices. The unique displays of the presentdisclosure transform how market prices interact with weather data in thefinancial community. The displays of the present disclosure allow usersto convert more weather and price data into actionable knowledge, and ina manner that is faster than conventional systems.

The weather integration system of the present disclosure are also uniquein that it fully integrations two unique workflows (weather and marketdata, an example of disparate data structures) that are conventionallyhandled in a completely separate manner, because conventional systemswere unable to integrate the two streaming workflows due to thetechnical complexities of the weather and market workflows. Instead, atbest, some conventional trading desktops may simply provide access toweather (e.g., via i-frames) but cannot provide integrated weather andmarket data (e.g., weather data overlaid with market data). The weatherintegration system of the present disclosure (including the end-to-endinfrastructure) is the first and only weather integration system of itskind. In some examples, the weather integration system may provideopportunities to scale electronic trading operations geared to leveragechanging weather perspectives across many different asset classes, andmay provide unique displays that improve identification of tradingopportunities, including faster identification of trading opportunities.

In some examples, the weather integration system may derive one or morepreliminary daily forecast variables (e.g., daily average temperature,gas weighted degree day (GWDD), heating degree day (HDD), cooling degreeday (CDD), etc.), and may provide a “% Complete” value prior to theparticular model's completion of that forecast day. In other words, eachforecast day may have twenty four forecast model hours. When the noonforecast arrives, twelve of the twenty four possible forecast modelfiles exist, in the public domain, so that the forecast day is 50%complete. When the 1 pm forecast model data arrives, the forecast day isnow 54% complete, and so on. This innovative approach provides usersvaluable preliminary daily forecast data which may be directionallyaccurate. In other words, users may be presented a forecast day before(e.g., approximately about 4 minutes before) other weather vendors posttheir daily forecast data (from the same government weather forecastmodel).

In some examples, the weather integration system may provide an improvedspeed of understanding of weather and market data. The unique weatherworkflows (weather alpha and perspective workflows, described furtherbelow) allows users to make more informed and faster weather and pricedecisions. The same centralized weather workflows may easily allow auser to scale this unique process across an electronic trading floor andacross electronically traded instruments, thereby allowing each traderto more easily monitor multiple traded markets, as it relates tochanging weather perspectives (e.g., with greater accuracy and fasterspeed).

In some examples, the weather integration system may providecomprehensive model data, including higher resolution forecast data fromgovernment entity models. Because the weather integration system mayprovide a low latency infrastructure, the weather integration system, insome examples, may be configured to move large amounts of data aroundthe world in seconds. This unique infrastructure may be leveraged toextract higher resolution versions of various forecast data including,in some examples, higher resolution versions of the GFS, GFS ENS, ECMWFand ECMWF ENS models. In some examples, the weather integration systemmay provide model data with enhanced spatial resolution (e.g., ¼ degree,whereas conventional resolution may be ½ degree) and enhanced time(temporal) resolution. In some examples, enhanced spatial resolution mayprovide a slightly more accurate weather model version (e.g., picking upon micro climates) which lower resolution versions may not be able toprovide. In some examples, enhanced temporal resolution may includehourly time steps, meaning that users may receive forecast updates, forexample, every 20 seconds. In contrast, conventional temporal resolutionmay be about three hourly updates which may occur every 60 seconds. Inaddition, in some examples, twenty four model hours (e.g., time steps)may be included in the first five days (120 hrs) of the GFS weatherforecast model.

In some examples, the weather integration system may leverage the uniqueweather symbology combined with streaming market price data (e.g.,market data stream(s) together with a trading desktop functionality tocreate an almost limitless combination of symbol element (“WeatherLegos”) designs to provide unique interactive GUIs, client applications,client services and trading desktop applications. In some examples, theweather symbology is configured to treat weather data like a tradedinstrument, so any weather symbol may be entered directly into a chart,table, watchlist, etc. to view the weather data directly. In someexamples, the weather symbology may be configured to operate in tradingdesktops, spreadsheet applications and with one or more object-orientedprogramming languages (e.g., Python™).

In some examples, weather data may be accessed in real-time using thesymbol elements, and the weather integration system may be configured toleverage both streaming weather data and streaming price data inside anelectronic financial desktop. The unique weather symbol elements mayalso allow weather data to be accessed from one or more separatedirections, including, in some examples three primary weatherperspectives, including guidance, progression and (forecast) accuracyperspectives.

In some examples, the guidance perspective may be configured to assessweather forecast risk and confidence. For example, if all of the weatherforecasts agree, there is less risk embedded into the market prices.Alternatively if there is a wide range in the forecasts, then there isgreater risk (less confidence) in the perceived future weather,presenting greater price volatility of the market prices. In someexamples, the progression perspective may be configured to assess a‘run-to-run’ forecast volatility as well as how all weather forecastmodels relate to each other. In some examples, the progressionperspective may use the principles of convergence and mean reversion tohelp users spot short-term and longer-term electronic tradingopportunities. In some examples, the accuracy perspective may besuitable for users who take (or make) physical delivery ofweather-related instruments such as power, natural gas, natural gasliquids and the like. For example, often there is a disconnect betweenthe perception of the weather, at the time a monthly futures contractexpires, versus what weather will actually occur inside of that month.It is important to understand the probability a weather forecast will beaccurate (or inaccurate). The accuracy perspective may aid in such anunderstanding.

Referring now to FIG. 1 , a functional block diagram of an example datadistribution environment 100 (environment 100 herein) is shown.Environment 100 may include data integration/distribution (DID) system102, one or more weather data sources 104, one or more market datasources 106 and one or more user devices 108 (associated with at leastone user). In some examples, one or more components of environment 100(e.g., DID system 102, weather data source(s) 104, market data source(s)106 and/or user device(s) 108) may be communicatively coupled via one ormore networks 110. Network(s) 110 may include, for example, a privatenetwork (e.g., a local area network (LAN), a wide area network (WAN),intranet, etc.) and/or a public network (e.g., the Internet).

Weather data source(s) 104 may include, without being limited to,weather forecast model sources, one or more weather observations datasources associated with one or more locations and the like. In someexamples, sources for weather forecast model(s) may provide weathermodel data for generating weather forecasts for one or more geographicalregions. In one non-limiting example, the weather forecast modelsource(s) may include one or more of National Oceanic and AtmosphericAdministration (NOAA) United States (US) Global Forecast System (GFS),NOAA GFS global ensemble (GFS ENS), NOAA GFS global ensemble Extension(GFS ENS EXT), NOAA's Climate Forecast System Ensemble model (CFS ENS),European Center for Medium-Range Weather Forecast (ECMWF), ECMWFEnsemble, ECMWF Ensemble Extension (ECMWF EXT), ECMWF Seasonal model(SEAS) and its corresponding extension model (SEAS EXT) and othergridded binary format (GRIB) weather forecast model source(s). Ingeneral, a weather forecast model source may run a weather forecastmodel (e.g., periodically such as quarterly, monthly, multiple times perweek, one or more times per day, asynchronously, in response to apredetermined condition, etc.) and may provide weather forecast data forup to a predetermined number of days. For example, the model for the GFSis run four times a day and may produce forecasts for up to 16 days inadvance and run, for example, four times per day. As another example,the CFS ENS may run daily and may forecast out nine months into thefuture. In one non-limiting example, source(s) for weather observationsdata may include one or more of Meteorological Aerodrome Report (METAR)data and Climate Forecast System (CFS) data including CFS Reanalysis(CFS-R) data for one or more locations (e.g., one or more airports,weather stations, etc.). In some examples, CFS-R data may be used toprovide global observation estimates, for an even greater number ofweather parameters, as estimates which METAR sensors and/or limitedphysical locations may not provide. In general, weather observationsdata may be updated periodically (e.g., hourly, daily, monthly,quarterly, etc.), and may include various weather data (e.g.,temperature, dew point, wind direction, wind speed, precipitation, cloudcover, visibility, barometric pressure and the like, as well as derivedvalues such as GWDD) for one or more weather observation locations. Ingeneral, weather data source(s) 104 may include any suitable weatherdata sources for weather forecast model(s) and weather observations dataassociated with one or more locations. In general, weather datasource(s) 104 that may be in communication with DID system 102 maycomprise a server computer, a desktop computer, a laptop, a smartphone,or any other electronic device known in the art configured to capturedata, receive data, generate weather forecast model data, store dataand/or disseminate any suitable weather data.

Market data source(s) 106 may include, in general, any electronic sourcefor market data (e.g. price data and/or trade-related data associatedwith one or more tradeable financial instruments). Non-limiting examplesof types of market data that may be provided by market data source(s)106 may include one or more of equities data, derivatives data, dataassociated with one or more indices, market depth data, energy marketdata, fundamental data, inter-dealer broker (IDB) data andover-the-counter (OTC) market data. In some examples, market datasource(s) 106 may also include one or more news sources that may provideinformation associated with market data (e.g., observations on marketdata trends, news stories that may affect market data and the like). Insome examples, fundamental data may include one or more sources whichcontain structured and/or non-structured data which may provideinformation associated with market data impacting supply, demand and/ortransportation (such as shipping data, electricity emissions, naturalgas pipeline flows, etc.). In general, market data source(s) 106 thatmay be in communication with DID system 102 may comprise a servercomputer, a desktop computer, a laptop, a smartphone, or any otherelectronic device known in the art configured to capture data, receivedata, store data and/or disseminate any suitable market data.

User device(s) 108 may include, without limit, any combination of mobileand/or stationary communication device such as mobile phones, smartphones, tablets computers, laptop computers, desktop computers, servercomputers or any other computing device configured to capture, receive,store and/or disseminate any suitable data. In some examples, userdevice(s) 108 may include one or more external computer systemsconfigured to receive weather and/or market data as processed by DIDsystem 102, and may provide additional analysis, user interaction and/ordistribution functionality. In one embodiment, user device(s) 108 mayinclude a non-transitory memory, one or more processors includingmachine readable instructions, a communications interface which may beused to communicate with DID system 102, a user input interface forinputting data and/or information to user device(s) 108 and/or a userdisplay interface for presenting data and/or information on userdevice(s). In some examples, the user input interface and the userdisplay interface may be configured as a graphical user interface (GUI)(such as interactive GUI 900 shown in FIGS. 9A-9H). User device(s) 108may also be configured to provide interactive GUI 120 of DID system 102on the GUI of user device(s) 108. In some examples, user device(s) 108may include computer system 1100 (shown in FIG. 11 ).

DID system 102 may include data collector 112, data feed distributor114, weather integration server 116, time series server 118, interactiveGUI 120, one or more data caches 124, one or more client applicationsand/or services 126, one or more data caches 124, and client/serverconnection manager 128. In some examples, one or more components 112-128of DID system 102 may communicate with each other via a data and controlbus (not shown). Although DID system 102 is shown in FIG. 1 as onecomponent (e.g., a server), DID system 102 may include one or morecomponents (e.g., one or more servers), whether co-located or linkedacross one or more networks.

Although not shown, DID system 102 may include at least one processor(e.g., processing device 1102 shown in FIG. 11 ) and non-transitorymemory (e.g., memory 1106 shown in FIG. 11 ) storing one or moreroutines and or algorithms for performing the functions of DID system102 described herein. An example implementation of one or morecomponents of DID system 102 is shown by computer system 1100 (shown inFIG. 11 ).

In some examples, DID system 102 may obtain weather data and market datafrom among respective weather data source(s) 104 and market datasource(s) 106 via data collector 112. Although not shown, data collectormay include one or more input and/or output interfaces (e.g., anelectronic device including hardware circuitry, an application on anelectronic device) for communication with other components ofenvironment 100 (e.g., weather data source(s) 104 and market datasource(s) 106 (and, in some examples user device(s) 108).

Data collector 112 may be configured to obtain weather and market datathrough any suitable electronic data collection technique. For example,data collector 112 may obtain data through or more data feeds (includingstreaming (live) data feed(s)), one or more file transfers (including,in some examples, one or more secure file transfers), by data beingpushed to DID system 102 and/or by DID system 102 pulling and/orextracting data and/or information from among weather data source(s) 104and/or market data source(s) 106. In some examples, data collector 112may include security protection (e.g., encryption, decryption) toprotect the integrity of the obtained data.

In some examples, data collector 112 may perform one or more offiltering, data normalization, data reformatting, data aggregation andthe like. In some examples, electronic data that may be obtained by datacollector 112 may include data that may be unable to be processed, datathat includes one or more errors and the like. In some examples,different sources among weather data source(s) 104 and market datasource(s) 106 may transmit data with various unique, non-standard valuesand/or data formats (e.g., proprietary formats). Furthermore, datacontent may correspond to different forms of data, such as differentcurrencies, date formats, time periods, etc.

Non-limiting examples of data filtering that may be performed by datacollector 112 may include excluding null data values, excludingcorrupted data, excluding outlier data values (e.g., a data valueoutside of a pre-defined value range, outside of a pre-defined timerange) and the like. In some examples, data collector 112 may reformatthe collected data to one or more common formats and/or normalize thecollected data. In some examples, data collector 112 may be configuredto aggregate and/or combine at least a portion of the collected data(e.g., according to one or more pre-defined categories (such as a typeof data, one or more predetermined time periods, etc.)).

Data feed distributor 114 may be configured to receive the collecteddata from data collector 112. Data feed distributor 114 may also beconfigured to communicate with weather integration server 116 and timeseries server 118. In some examples, data feed distributor 114 may alsobe configured to communicate with client application(s)/service(s) 126.In some examples, data feed distributor 114 may also be configured tocommunicate with data cache(s) 124.

In general, data feed distributor 114 may be configured to process thereceived data (e.g., the collected market and weather data), and maydistribute the received data to one or more among weather integrationserver 116, time series server 118, data cache(s) 124 and clientapplication(s)/service(s) 126 (not all connections with data feeddistributor 114 shown). Data feed distributor 114 may determine whichcomponent to distribute the received data to, based on one or morecharacteristics of the received data (e.g., data type, one or morepredetermined conditions, one or more predetermined parameters and thelike). In general, data feed distributor 114 may distribute weather dataamong the received data (collected from weather data source(s) 104) toweather integration server 116, and may distribute market data among thereceived data (collected from market data source(s) 106) to time seriesserver 118.

Weather integration server 116 may be configured to receive weather datafrom data feed distributor 114, including weather forecast model datafrom among one or more weather forecast data models and weatherobservation data from one or more locations. Weather integration server116 may be configured to communicate with time series server 118 andinteractive GUI 120. Weather integration server 116 may be configured tosegment (e.g., separate and/or index) the received weather data (fromamong the weather observations data and the weather forecast model data)into one or more segments in accordance with a predetermined weathersymbology. (Weather symbology is described further below). In someexamples, weather integration server 116 may also store at least aportion of the segmented weather data. Weather integration server 116may provide the segmented weather data to time series server 118. Insome examples, weather integration server 116 may also generate (andstore) one or more weather maps from the weather forecast model data. Insome examples, weather integration server 116 may provide weather map(s)to interactive GUI 120. In general, weather integration server 116 mayprovide segmented weather data to time series server 118 (as well asweather map(s) to interactive GUI 120) that may include real-time (e.g.,streaming) data, near-real-time data, historical (e.g., static data)and/or any combination thereof.

In some examples, the segmented weather data may be generated to provide(weather symbology-segmented) weather data to time series serve 118 as afunction of exchange time and/or interval time. Importantly, thesegmented weather data, as generated by weather integration server 116,is in a format that can be readily integrated with market data withintime series server 118. In some examples, the segmented weather data maybe automatically updated based on (i.e., updated concurrent with)changes to the received weather data (e.g., new observation data, anyupdates to the weather forecast model data, etc.).

Time series server 118 may be configured to receive market data fromdata feed distributor 114 and segmented weather data t from weatherintegration server 116. Time series server 118 may also receive at leastone weather data request (e.g., via interactive GUI 120, via clientapplication(s)/service(s) 126). In some examples, the weather datarequest may be associated with at least one symbol element, and may beconverted to weather symbology instruction. Time series server 118 mayextract one or more portions of the segmented weather data (receivedfrom weather integration server 116) in accordance with the weathersymbology instruction. In general, the weather symbology instruction mayinclude one or more symbol elements (such as forecast location, weatherperspective, weather model). In some examples, the weather symbologyinstruction may also include one or more variables (e.g., field(s)and/or condition(s)). (Examples of weather symbology instructions andweather perspectives are described further below.) Time series server118 may be further configured to integrate the extracted weather data(in accordance with the weather symbology instruction) with at least aportion of market data (e.g., received from data distributor 114) toform an integrated presentation package. The integrated presentationpackage may be provided to interactive GUI 120 and/or clientapplication(s)/service(s) 126 (including, in some examples, at least oneapplication programing interface (API)).

In some examples, time series server 118 may include a tick engine andat least one database, for processing large amounts of market data thatmay change rapidly (e.g., user orders, market events, quotes, etc.).Time series server 118 may also include a presentation tool forgenerating presentation packages, including integrated weather andmarket data presentation packages. For example, time series server 118may combine the extracted weather data (including, for example, weatherforecasts, weather observations, weather symbology indications) with atleast a portion of the market data (e.g., based on user input,pre-defined parameters, etc.) to form at least one integratedpresentation package suitable for presentation (and interaction) (e.g.,on interaction GUI 120, via an API, etc.). Although examples aredescribed where presentation package includes both weather and marketdata, in some examples, at least one presentation package may begenerated that includes (packaged) extracted weather data.

Although not shown, time series server 118 may include a controller(e.g., at least one processor, a microcontroller and the like, such asprocessing device 1102 shown in FIG. 11 ) and non-transitory memory(e.g., memory 1106 shown in FIG. 11 ) storing one or more routines andor algorithms for performing the functions of time series server 118described herein. An example implementation of one or more components oftime series server 118 is shown by computer system 1100 (shown in FIG.11 ).

The integrated presentation package may include any suitable data and/orinformation (including weather data, market data, other suitable dataand/or any combination thereof) configured in a manner for presentationand/or user interaction, including, but not limited to, one or more ofat least one chart, at least one map, at least one watchlist, at leastone alert, at least one grid application, at least one table, user inputoptions including weather symbology input options and the like, In someexamples, at least a portion of the data and/or information presented inthe integrated presentation package may be user-customizable (includingvia the use of weather symbology). In some examples, the data and/orinformation in the presentation package may include one or more (live)data streams, such that the data and/or information presented by thepresentation package may be updated concurrently with the data in thedata stream(s). In some examples, the presentation package may alsoinclude historical (e.g., static data). In some examples, thepresentation package may include at least one interactive weather gridthat may be configured to allow user selection of a portion of the grid(e.g., clicking on a particular area with a pointing device). Responsiveto the user selection, interactive GUI 120 may generate a predeterminedstreaming view of weather and market data associated with the selectedportion.

An example of weather integration server 116 together with time seriesserver 118 is described further below with respect to FIG. 2 .

Interactive GUI 120 may be configured to generate weather impactdashboard 122 having a uniquely configured arrangement of one or moreinput regions, one or more notification regions and one or more displayregions. In some examples, one or more portions of weather impactdashboard 122 may be automatically updated (including in real-time suchas streaming data or near real-time) responsive to changes in weatherdata and/or market data. In some examples, the display region(s) mayinclude an interactive display that permits/prompts user input and maybe automatically updated in response to user input.

In some examples, weather impact dashboard 122 may include differentconfigurations based on an underlying application and/or service (e.g.,among client application(s)/service(s) 126 for which it is launched. Forexample, weather impact dashboard 122 may have a first configuration fora mobile application, may have a second (different) configuration for adesktop application and may have a third (different) configuration for aspreadsheet application. In some examples, weather impact dashboard 122may include one or more windows with different configurations dependingupon a particular weather perspective. In some examples, weather impactdashboard 122 may provide user input of a weather symbology instructiondirectly (e.g., a weather data request may include a weather symbologyinstruction itself). In some examples, weather impact dashboard 122 mayprovide one or more user input prompts that may be converted to aweather symbology instruction.

Examples of interactive GUI 120 are described further below with respectto FIGS. 9A-10F.

In some embodiments, DID system 102 may include data cache(s) 124 (e.g.,a hardware component and/or software component) for storing data and/orinformation associated with the various functions of DID system 102.Data cache(s) 124 may be configured to store collected data (e.g., bydata collector 112 and distributed by data feed distributor 114),including, for example, weather data from among weather data source(s)104 and market data from among market data source(s) 106. In someexamples, data cache(s) 124 may store requested weather datasets(generated by weather integration server 116) and/or integratedpresentation package(s) (generated by time series server 118). Ingeneral, data cache(s) 124 may be configured to store any data in whichfaster data retrieval of the data for future requests may be useful. Insome examples, data cache(s) 124 may include a data manager (DM) (notshown) for controlling collection and/or retrieval of data in datacache(s) 124.

In some examples, DID system 102 may include storage (e.g., one or moredatabases) to store any parameters, configurations, functions and/orother suitable data and/or information that may be useful for one ormore of components 112-128. In some examples, the storage may beconfigured to store data distributed by data feed distributor 114 and/ordata collected by data collector 112.

In some examples, DID system 102 may include clientapplication(s)/service(s) 126 for creating instances of application(s)and/or service(s) for distributing data to user device(s) 108. In onenon-limiting example, client application(s)/service(s) 126 may includeone or more of a trading desktop, a spreadsheet application, a mobileapplication (e.g., an application that may be suitable for displayscreen of a mobile device such as a smartphone) streaming (e.g. raw,normalized, filtered and/or aggregated) data feeds and/or one or moreAPIs for receiving data in one or more object-oriented programminglanguages (e.g., Python™, R, etc.). In some examples, clientapplication(s)/service(s) 126 may create instance(s) of application(s)and/or service(s) including interactive GUI 120 having at least oneconfiguration of weather impact dashboard 122. In some examples, DIDsystem 102 may be configured to expose a presentation package to one ormore API(s) among client application(s)/service(s) 126.

In some examples, DID system 102 may include a client/server connectionmanager 128 (also referred to as connection manager 128) configured tomanage client to server connection requests. In general, connectionmanager 128 may manage connection request(s) of user device(s) 108 toDID system 102, to access client application(s)/service(s) 126.

Referring next to FIG. 2 , a functional block diagram of example weatherintegration server 116 is shown. Weather integration server 116 mayinclude observations collector 204, one or more databases 206,forecast/observation generator 210, map generator 212, weather symbologystorage 214, storage 216 for one or more weather structures and one ormore databases 220. In some examples, one or more components 204-216 and220 of weather integration server 116 may communicate with each othervia a data and control bus (not shown).

Although not shown, weather integration server 116 may include acontroller (e.g., at least one processor, a microcontroller and thelike, such as processing device 1102 shown in FIG. 11 ) andnon-transitory memory (e.g., memory 1106 shown in FIG. 11 ) storing oneor more routines and or algorithms for performing the functions ofweather integration server 116 described herein. An exampleimplementation of one or more components of weather integration server116 is shown by computer system 1100 (shown in FIG. 11 ).

Observations collector 204 may be configured to obtain weatherobservations data 202 associated with one or more weather observationlocations (e.g., from among weather data source(s) 104). In anon-limiting example, weather observations data 202 may include METAR,CFS-R observations data and CFS-R generated climatological data (e.g., atrailing 10 year climatology, a trailing 15 year climatology, a trailing30 yr Climatology, etc.). In some examples, observations collector 204may be configured to separate METAR and CFS-R observations data, CFS-Rclimatology data, and may process each type of data separately. In someexamples, observations collector 204 may be configured to parse weatherobservations data 202, to identify one or more elements of weatherobservation data 202 that may be useful for generating segmented weatherdata 218. In some examples, observations collector 204 may generate oneor more identifiers for the identified elements of the (parsed) weatherobservations data 202. In some examples, the identifier(s) may includean observation date, a time as to when the weather observation wasobserved and/or a time-stamp indicating when a particular value/set ofvalues was received.

Observations collector 204 may also store observations data 202 (afterparsing) in database(s) 206 (e.g., as historical observations).Database(s) 206 may store observations data in any suitableformat/arrangement for efficient data storage and retrieval. In someexamples, database(s) 206 may store (parsed) weather observations data202 based on identifiers generated by observations collector 204.Observations collector 204 may also provide at least a portion ofweather observations data 202 (e.g., after parsing and/or fromdatabase(s) 206 to forecast/observation generator 210.

Forecast/observation generator 210 may be configured to obtain weatherforecast model data 208 (e.g., from among weather data source(s) 104).In a non-limiting example, weather forecast model data 208 may includeweather forecast models from GFS, GFS ENS, GFS ENS EXT, CFS ENS, ECMWF,ECMWF ENS, ECMWF ENS EXT, SAEAS and SEAS EXT forecast model sources. Inone example, one or more (in some examples all) forecast models mayoriginate in a GRIB file format and may be instantly converted into citylevel data for forecast valid times for a number of weather forecastvariables, which may then be immediately run though time series server118 so the data can stream through DID system 102. Forecast/observationgenerator 210 may also obtain weather observations data 202 fromobservations collector 204 (and/or form database (s) 206).Forecast/observation generator 210 may also be configured to communicatewith weather symbology storage 214 and weather structure(s) storage 216.In general, forecast/observation generator 210 may be configured to usepre-defined symbol elements (stored in weather symbology storage 214) tosegment forecast model data 208 and/or observations data 202 (e.g., viaobservations collector 204 and/or stored observation(s) via database(s)206) into one or more pre-defined segments of weather data, to formsegmented weather data 218. In some examples, at least a portion offorecast model data 208 may be stored in one or more databases (notshown), and forecast/observation generator 210 may use at least aportion of previously stored forecast model data to generate segmentedweather data 218. Segmented weather data 218 may be provided to timeseries server 118.

Weather symbology storage 214 may be configured to store a pre-definedweather symbology. The pre-defined weather symbology may include one ormore pre-defined symbol elements, one or more pre-defined variables(e.g. pre-defined condition(s) and/or fields) and one or morepre-defined rules for combining and/or arranging symbol elements into atleast one weather symbology instruction having a pre-defined instructionstructure. The symbol elements may be linked to respective segments ofthe weather data (including, in some examples, segments of weather datastreams). The weather data may be segmented, (by forecast/observationgenerator 210) in accordance with the symbol elements of the weathersymbology stored in storage 214. An example weather symbology is shownin FIG. 3C. In some examples, a weather symbology instruction may beused to extract portions of segmented weather data (e.g., by time seriesserver 118) to create integrated presentation package 226.

Weather structure(s) storage 216 may be configured to store one or morepre-defined weather structures having one or more respective pre-definedrules (e.g., software workflows) for generating one or more pre-definedweather alpha workflows and one or more pre-defined weatherperspectives. Time series server 118 may use the pre-defined weatherstructure(s) to create integrated presentation package 226. In general,the pre-defined weather perspective(s) may represent workflows (e.g.,having one or more pre-defined rules) for converting segmented weatherdata 218 into user-customizable actionable knowledge (e.g., providingone or more different ways to assess various aspects of segmentedweather data 218 that may not be directly observable by simplypresenting weather forecast(s) and/or weather observation(s)). In anon-limiting example, the weather perspective(s) may include one or morepre-defined rules for generating integrated presentation package 226 inaccordance with one or more of a guidance workflow, a progressionworkflow and an accuracy workflow. Examples of weather perspectives aredescribed further below. In a non-limiting examples, the one or morepre-defined weather alpha workflows may include pre-defined rules forgenerating at least one of a weather macro alpha and a weather microalpha (described further below).

In general, a weather symbology instruction (associated with weatherdata request 220), may be formed (e.g., by time series server 118)having the pre-defined instruction structure, using weather symbolelement(s) and variable(s) in accordance the pre-defined rule(s) storedin weather symbology storage 214. In some examples, the weathersymbology instruction may include a weather structure (e.g., aperspective), an observation location and a weather forecast model. Theweather symbology instruction may include additional condition and/orfunction information, such as one or more of a model run, forecast validdays, forecast valid hours, etc. In some examples, the weather symbologyinstruction may be created based on one or more data requests 224 (e.g.,received via user device(s) 108). Predefined rule(s) associated with theweather structure (of the weather symbology instruction) may be obtainedfrom weather structure(s) storage 216 and may be used to createintegrated presentation package 226. In some examples, integratedpresentation package 226 may include at least a portion of segmentedweather data 218 (e.g., based on a weather alpha workflow and/or aweather perspective) integrated together with market data 222 (receivedby time series server 118). In some examples, integrated presentationpackage 226 (at least a portion) may include at least a portion ofsegmented weather data 218 (e.g., without any market data 222).

Although weather symbology storage 214 and weather structure(s) storage216 are shown as being part of weather integration server 116, storagecomponents 214 and/or 216 may be external to weather integration server116. As shown in FIG. 2 , time series server 118 may be communicativelycoupled to storage components 214 and 216.

Map generator 212 may receive at least a portion of forecast model data208, and may render one or more weather forecast maps via any suitablewell-known rendering technique. Map generator 212 may also store one ormore weather forecast maps in database(s) 220. Database(s) 220 may storeweather forecast map(s) in any suitable format/arrangement for efficientdata storage and retrieval. One or more weather maps may be provided tointeractive GUI 120 (e.g., via database(s) 220 and/or via map generator212). Examples of types of maps that may be rendered are describedfurther below with respect to FIG. 10C.

In operation, forecast/observation generator 210 may create segmentedweather data of the collected (e.g., streaming) forecast and/orobservations data) in accordance with the pre-defined symbol elements(and in some examples, symbology variables) stored in storage 214. Insome examples, the weather data may be segmented by indexing portions ofthe weather data to the (linked) symbol elements (and symbologyvariables in some examples) and/or separating the weather data intosubsets linked to the symbol elements (and symbology variables in someexamples). In some examples, at least a portion of segmented weatherdata 218 may also be stored in one or more databases (not shown). Timeseries server 118 may receive at least one (weather) data request 224(e.g., from user device(s) 108 via interactive GUI 120). Response todata request 224, time series server 118 may convert data request(s) 224to a corresponding weather symbology instruction, based on pre-definedweather symbology rule(s) in weather symbology storage 214 (or mayreceive the weather symbology instruction directly in data request 224).Time series server 118 may determine which segment(s) of segmentedweather data 218 to extract based on the symbol element(s) in theweather symbology instruction (that are linked to segment(s) ofsegmented weather data). Time series server 118 may also determine aparticular weather structure among weather structure(s) stored instorage 216, based on the weather symbology instruction. Time seriesserver 118 may create integrated presentation package 226 in accordancewith corresponding pre-defined weather structure rules (e.g., workflow)for the particular weather structure. In some examples, time seriesserver 118 may stitch together a weather forecast in accordance with theweather symbology instruction, by extracting segment(s) of segmentedweather data 218 according to the particular weather structure.Moreover, time series server 118 may generate integrated presentationpackage 226 as a function of multiple time series formats, includingexchange time and interval time, such that extracted segment(s) ofsegmented weather data 218 may be easily integrated with market data 222by time series server 118, so that end users (e.g., via interactive GUI120, via client application(s)/service(s) 126) may readily identify anyimpacts of weather data on market data 222.

In some examples, integrated presentation package 226 may be generatedbased on predetermined parameters (e.g., determined by weatherintegration server 116, determined by time series server 118, defined bythe user, etc.), without receiving any data request 224 (and/orindependent of any data request 224). For example, an initial launchpage on weather impact dashboard 122 of interactive GUI 120 may begenerated based on the predetermined parameters (via extracting portionsof segmented weather data 218 in accordance with the predeterminedparameters). A user of user device(s) 108 may then modify and/orcustomize integrated presentation package 226 that is ultimatelypresented on weather impact dashboard 122 by data request(s) 224.

Weather Workflows Overview

Before describing details of the symbology structure, an overview ofexample weather workflows (e.g., weather alpha and weather perspectives)of the present disclosure for interacting with weather data is provided.The weather alpha and weather perspectives workflows are unique to thepresent disclosure and have never been integrated into a trading desktopor any system (including any streaming system) containing market pricesprior to the present disclosure. Although the present disclosuredescribes three primary weather perspective workflows, it is understoodthat the present disclosure is not limited to the example workflowsdescribed below, and that any suitable weather workflow for interactingwith weather and market data to provide meaningful indications ofweather impact on market data are also within the scope of the presentdisclosure. In some examples, the weather perspective and weather alphaworkflows may be used by any suitable end-user including, without beinglimited to, traders, analysts, meteorologists, trading floor quants,investors, hedgers and the like.

Weather Alpha: A system which allows for a data display or chartingdisplay of weather forecast variables (like temperature, Degree Day,GWDD, wind, humidity, etc.) from a specific weather forecast model ormultiple weather forecast models, initialized and released at a specifictime of day (model run) from which a specific location or locations(e.g., city or region) which may (or may not) include preliminaryestimated forecast values such as ‘% complete’ or ‘Fast& Full’ orpartial week month or seasonal aggregations called “Progress” orpre-calculated (streaming) values (i.e. “Change” from previous,“Anomaly/Difference” from Climatology) to be displayed in real-time,alongside market prices for any traded instrument which includes but isnot limited to one or more traded commodities, equity or bondinstruments which may or may not include futures, forward and/or varioustypes of option contracts. The ‘weather symbology’ of the presentdisclosure allows the user a method to easily access weather forecastdata in at least one of a “Seasonal”, “Monthly” “Weekly”, “Daily” and“Hourly” format in a manner consistent for data Analysis or Chartingand/or aligning with other market data. See FIGS. 4A-4D (discussedfurther below). In general, an objective of weather alpha may includeproviding one or more tools to quickly understand the vast amount ofstreaming data specifically related to changing weather perceptions anda magnitude of weather forecast changes directly to (changing) prices ofany traded instruments (e.g., on an electronic exchange system and/oroffline of an electronic exchange system).

The example three primary weather perspective workflows may include:

-   -   1) Guidance: A system which allows for a data display, or        charting display, of a weather forecast variable (like        temperature, Degree Day, GWDD, wind, humidity, etc.) from        MULTIPLE weather forecast models, initialized and released at        one or more specific times of day (model runs) from which a        specific location or locations (e.g., city or region) which may        (or may not) include preliminary estimated forecast values such        as ‘% complete’ or ‘Fast& Full’ or partial week, month or        seasonal aggregations called “Progress” or pre-calculated        (streaming) value(s) (e.g., “Change” from previous and/or        “Anomaly/Difference” from Climatology) to be displayed in        real-time or its history, allowing the user to closely examine        weather forecast risks, by visualizing if all weather forecasts        are in agreement or disagreement with each other over the        forecast duration. The ‘weather Symbology’ of the present        disclosure allows the user a method to easily access weather        forecast data in a manner consistent for data Analysis or        Charting and/or aligning with other market data. See FIG. 5        (discussed further below). In some examples, Daily or Hourly        represent weather forecast fields. The symbology allows weather        forecasts to be treated as a continuation contract (e.g., such        as a prompt month natural gas contract) or revert to previous        weather forecasts. Data (including in some examples all data) in        DID system 102 may be displayed as a function of receipt time or        interval start time. In some examples, the Symbology may include        an MR0 format (described herein).    -   2) Progression: This style of chart may hold a particular        Forecast Valid Date/Time of Day on that specific Date constant        (called a “Target Date”) and shows how the weather forecast        models have changed overtime, leading up to that “target date”.        The system which allows for either a data display or charting        display of a weather forecast variable (like temperature, Degree        Day, GWDD, wind, humidity, etc.) from MULTIPLE weather forecast        models, and any number of model runs, for a specific location        (city or region) which may (or may not) include preliminary        estimated values such as ‘% complete’ or ‘Fast& Full’ or partial        week, month or seasonal aggregations called “Progress” or        pre-calculated forecast value (i.e. “Change” from previous        and/or “Anomaly/Difference” from Climatology) to be displayed in        real-time, allowing the user to closely examine weather forecast        changes over time (to a point at which they all may converge).        The ‘weather Symbology’ of the present disclosure allows the        user a method to easily access weather forecast data in either a        “Seasonal”, “Monthly” “Weekly”, “Daily” or “Hourly” format in a        manner consistent for data Analysis and/or Charting and aligning        with other market data. See FIGS. 6A-6C (discussed further        below).    -   3) Accuracy: This style of chart or data query may look back at        historical weather forecast ‘model run dates’ and ‘model runs’        and hold a Forecast Valid Day constant. For example ‘Forecast        Day #1’ could be examined over the last 30 days of weather        forecasts from a particular weather forecast model. Each of        these Day 1 weather forecasts (which refer to a different        Forecast Valid Date) can then be subtracted from their        respective weather observation (then all (e.g., 30) data points        may be averaged) to derive an average weather forecast Bias        (hotter/colder) or other performance statistics. The ‘weather        Symbology’ of the present disclosure allows the user a method to        easily access weather forecast data in either a “Daily” or        “Hourly” format in a manner consistent for data Analysis or        Charting and/or aligning with other market data. See FIGS. 7A        and 7B (discussed further below).

Overview of Weather Symbology

To accomplish the example weather perspective and weather alphaworkflows (which may be important, for example, to traders, analysts,meteorologist and trading floor quants, investors, hedgers), lies anunderlying comprehensive ‘weather symbology’. This symbology structureis desirable for weather data to function inside a streaming time seriesserver-based trading desktop (such as time series server 118), where thetime series server also accommodates a fast streaming delivery of marketprices. It is not the order of the elements listed in the ‘weathersymbology’ but rather the function of what weather ‘elements’ can beextracted and applied to client application(s)/service(s) 126 (such as atrading desktop) which hosts market prices. To describe the methodologyof the ‘weather symbology’, a unique structure is established by thepresent disclosure to mimic each of the three primary weatherperspective workflows.

-   -   1) Guidance based weather symbology may use a ‘ location’, a        ‘Weather Model Name’ along with a specific ‘Weather Model Run        Date’ and a ‘Weather Model Run’ to extract any weather forecast,        initialized and produced any time of day, for either current        running forecasts or historical weather forecasts. Along with        that functionality, users may have shortcut codes, meaning a        user may obtain the most current weather forecast for that        ‘Location’, ‘Weather Model Name’ or ‘Weather Model Run’. In        addition, the Guidance based weather symbology structures may        allow for either “specific” or “rolling” symbols, meaning a user        can request a specific ‘Weather Model Run Date’ and/or specific        ‘Model Run’ or “rolling”. From that core information, the        Guidance weather symbol can be further extended to include        calendar, seasonal, monthly, weekly hourly or daily weather        forecast data fields, for any specific location, for any weather        forecast variable, for any preliminary estimated values such as        ‘% complete’ or ‘Fast& Full’ or progress, or pre-calculated        values (e.g., “Change” from previous and/or “Anomaly/Difference”        from Climatology) or Ensemble based statistics in the symbol        itself. All of this weather information can then be easily        combined in a manner consistent for data Analysis, Charting        and/or aligning with other market data in either “Exchange Time”        or “Interval Start” time. See FIG. 5 and the description herein        for constructing the weather symbology.    -   2) Progression based weather symbology may use a ‘location’, a        ‘Weather Model Name’ and an optional ‘Weather Model Run’ to        extract all weather forecasts initialized and produced for a        specific “target Date”. The Progression based weather symbols        can accommodate any weather forecast, produced any time of day,        for current running forecasts and historical weather forecasts.        Along with the functionality users may have shortcut codes,        meaning a user may obtain the most current weather forecast for        that ‘Location’, ‘Weather Model Name’ or ‘Weather Model Run’. In        addition, the Progression based weather symbology structure may        allow for either “specific” or ‘rolling symbols’, meaning a user        can request a specific or rolling ‘Target Dates’. From that core        information, the Progression weather symbol can be further        extended to include calendar, seasonal, monthly, weekly daily or        hourly weather forecast data, for any specific location, for any        weather forecast variable, for any preliminary estimated values        such as ‘% complete’ or ‘Fast& Full’ or Progress or        pre-calculated values (e.g., “Change” from previous and/or        “Anomaly/Difference” from Climatology) or Ensemble based        statistics in the symbol itself. All of this weather information        can then be easily combined in a manner consistent for data        Analysis, Charting and/or aligning with other market data in        either “Exchange Time” or “Interval Start” time. See FIGS.        6A-6C.    -   3) Accuracy based weather symbology may use a ‘location’, a        ‘Weather Model Name’ and an optional ‘Weather Model Run’ to        extract all weather forecasts produced for a specific time in        the future “Forecast Valid Day or Model Hour”. This symbol may        use the “!” for a rolling notation, so the user can always        extract a particular ‘Forecast Valid Day’ in the future. For        example a ‘Day 1’ may be a different “Date” with each new        ‘Weather Model Run Date’, so Day 1 is rolling. The Accuracy        based weather symbols can accommodate any weather forecast,        produced any time of day, and operate during current running        forecasts and historical weather forecasts. In addition the        Accuracy based weather symbology structure may allow for        ‘rolling symbols’ related to a “Forecast Valid Day” (e.g., as        opposed to a specific ‘Forecast Valid Date’/like used in a        Progression's ‘Target Date’). From that core information,        returned from the weather symbology, the Accuracy weather symbol        can be further extended to include, for example, calendar,        seasonal, monthly, weekly daily or hourly weather forecast data,        for any specific location, for any weather forecast variable,        for any ‘Fast& Full’ or Progress, or Ensemble based statistics        in the symbol itself. All of this weather information can then        be easily combined in a manner consistent for data Analysis,        Charting and/or aligning with other market data in either        “Exchange Time” or “Interval Start” time. See FIGS. 7A and 7B.

There are many sources of quality weather forecasts from variousgovernment entities, such as weather agencies, educational institutions,national research laboratories, military as well as private companies.The initial focus is from two primary government weather forecastentities; being the American government NOAA and European governmentECMWF. Each of the two entities produces multiple weather forecastproducts (a few examples of these weather forecast models include GFS,GFS ENS, GFS ENS EXT, CFS ENS, ECMWF, ECMWF ENS, and ECMWF ENS EXT,SEAS, SEAS EXT), which generally have the greatest influence on marketprices related to numerous traded instruments around the globe. Four ofthese weather forecast models are from the United States (GFS, GFS ENS,GFS ENS EXT, CFS ENS) and the remaining five (ECMWF, ECMWF ENS, ECMWFEXT, SEAS and SEAS EXT) are from Europe. Four of these weather ForecastModels are produced four times per day (Model Runs), the remaining fiveare produced in less frequent updates (e.g., daily or twice per week,etc.).

Tables 1 and 2 below include a list of weather forecast models andweather forecast variables which are included in the ‘weather symbology’of the present disclosure. In particular, Table 1 illustrates an examplelist of weather forecast models for the weather symbology of the presentdisclosure. Table 2 illustrates an example list of weather forecastvariables for the weather symbology of the present disclosure. In Table2, H represents an Hourly variable and D represents a Daily variable.

The ‘weather symbology’ described in the present disclosure may beconfigured to operate with all nine of these example weather models, aswell as any and all other weather forecasts, either in the public orprivate domain.

TABLE 1 Example list of weather forecast models for the weathersymbology CITY FORECAST DATA Weather Spatial Forecast Temporal ModelName Code Resolution Domain Model Runs Duration Resolution GFS GFS ¼degree Global 0z, 6z, 12z, 16 days Hourly-120 (aka 18 mile/ Forecast 18z0-384 hrs 3 hr 121-384 28 km grid) GFS GEFS ¼ degree Global 0z, 6z, 12z,16 days 3 hr-192 Ensemble (aka 18 mile/ Forecast 18z 0-384 hrs 6 hr198-384 28 km grid) ECMWF ECM ¼ degree Global 0z, 12z 10 days Hourly-90(aka 18 mile/ Forecast 0-240 hrs 3 hr 93-144 28 km grid) 6 hr 150-240ECMWF ECM ¼ degree Global 6z, 18z 10 days Hourly-90 (aka 18 mile/Forecast 0-240 hrs 28 km grid) ECMWF ECE ¼ degree Global 6z, 18z 15 daysHourly-90 ENS (aka 18 mile/ Forecast 0-360 hrs 3 hr 93-144 28 km grid)ECMWF ECE ¼ degree Global 0z, 12z 15 days Hourly 90 ENS (aka 18 mile/Forecast 0-360 hrs 3 hr 93-144 28 km grid) 6 hr 150-360 ECMWF ECMR ¼degree Global 2× per week 16-46 Daily ENS EXT (aka 18 mile/ ForecastMonday & days 28 km grid) Thursday CFS CFS ½ degree Global 0z only 0-9Daily Forecast months SEAS SEAS ¼ degree Global 1× month 0-7 Daily (aka18 mile/ Forecast months 28 km grid)

TABLE 2 Example (non-limiting) list of a weather forecast variables forthe weather symbology. Time Frame Field Name Front End Long ShortWEATHER META DATA SPECIFICS Time Receipt Time Receipt Time nstime Nstimenstime ns_exchange time ns_exchange time ns_exchange time Line_idLine_id Line_id sequence_number sequence_number sequence_numbersequence_series sequence_series sequence_series flags Flags flagsutcdatetime UTC Forecast Valid Date and UTC Date and Time Forecast ValidTme localdatetime LOCAL Forecast Valid Date and Local Date and TimeForecast Valid Tme fastvfull Ensemble Member fast vs full ENS Fast orFull filetime File Time File Time location Location Location ModelForecast Model Name Model Name modeldate Model Run Date MR Date modelrunForecast Model Run MR forecasthour Forecast Model Hour Mhr interpolatedInterpolated Value Intrpl blended Forecast and METAR are Blended Blendedlocaldate Local Date Local Date localhour Local Hour Local Hrensemblevariable Ensemble Variable Ens Varbl utcdate UTC Date UTC Dateutchour UTC Hour UTC Hr localforecastday Local Forecast Day Local Daypercentcomplete Percent Complete % Comp LIQUID PRECIPITATION H APCPAccum Precip 6 hr reset APCP H APCPNO Accum Precip hourly AccPrecip HIntrpl Interpolated D DAYPRECIP Daily Precipitation Daily Precip DDAYPRECIP_Chng_6 h Daily Precip 6 Hr Change D Precip 6 hr CHG DDAYPRECIP_Chng_12 h Daily Precip 12 Hr Change D Precip 12 hr CHG DDAYPRECIP_Chng_18 h Daily Precip 18 Hr Change D Precip 18 hr CHG DDAYPRECIP_Chng_24 h Daily Precip 24 Hr Change D Precip 24 hr CHG DDAYPRECIP_Diff_10 YAvg Daily Precip 10 yr Anomaly D Precip 10 yr ANOM DDAYPRECIP_Diff_15 YAvg Daily Precip 15 yr Anomaly D Precip 15 yr ANOM DDAYPRECIP_Diff_30 YAvg Daily Precip 30 yr Anomaly D Precip 30 yr ANOM DDAYPRECIP_Diff_30 YClimo Dally Precip Official 30 yr D Precip o30 yrANOM Anomaly SNOW & RUNOFF H WATR Snow Water Runoff SWRO H WATRNO SnowWater Runoff Hourly Runoff H Intrpl interpolated D DAYWATR Daily SnowWater Runoff D Runoff D WEASD Snow Water Equivalent SWE H WEASDNO SnowWater Equivalent Hourly SWE H Intrpl Interpolated D DAYWEASD Daily SnowWater Equivalent D SWE H SNOD Snow Depth SD D SNOD_Avg Daily Avg SnowDepth Avg SD SOLAR H DLWRF Downward Long Wave Radition Long Wave RadFlux H DLWRFNO Downward Long Wave Radition LWRad H intrpl Flux Hourlyinterpolated D DLWRF_Avg Downward Long Wave Radition LWRad D Flux DailyAvg H DSWRF Downward Short Wave Radition Short Wave Rad Flux H DSWRFNODownward Short Wave Radition SWRad H Intrpl Flux Hourly Interpolated DDSWRF_Avg Downward Short Wave Radition SWRad D Flux Daily Avg H GFLUXSurface Ground Heat Flux Grnd Heat Flux W/m{circumflex over ( )}2 HGFLUXNO Surface Ground Heat Flux Grnd Heat Flux H Intrpl W/m{circumflexover ( )}2 Hourly Intrpl H WILT Wilt hourly H Wilt D WILT_Avg Daily AvgSurface Ground Heat DAvg Gmd Heat Flux Flux W/m{circumflex over ( )}2WIND SPEED & DIRECTION H GUST Wind Gust max per hour Gust hr H WINDS_10m 10 Meter Wind Speed 10M W Speed H WINDD_10 m 10 Meter Wind Direction10M W Dir H TMP_80 m 80M Temp 80 m T H PRES_80 m 80 m Pressure 80 m PresH SPFH_80 m 80M Specific Humidity 80 m SpcH H WINDS_80 m 80M Wind Speed80 m WS H WINDD_80 m 89M Wind Direction 80 m WD AGRICULTURE D GUST_D_MAXDaily Avg Wilt Davg Wilt H SOILW_0_0.1 m Soil Moisture 0 cm 100 cm deepSoil Mo 0-100 cm D SOILW_0_0.1 m_Avg Daily Avg Soil Moisture 0 cm- DAvgSoil Mo 0-100 cm 100 cm deep H SOILW_0.1_0.4 m Soil Moisture 100 cm-400cm Soil Mo 100 cm-400 cm deep D SOlLW_0.1_0.4 m_Avg Daily Avg SoilMoisture 100 cm- DAvg Soil Mo 100 cm- 400 cm deep 400 cm H SOILW_0 4_1 mSoil Moisture 400 cm-1 m deep Soil Mo 400 cm-1 m D SOILW_0.4_1 m_AvgDaily Avg Soil Moisture 400 cm- DAvg Soil Mo 400 cm-1 m 1 m deep HSOILW_1_2 m Soil Moisture 1 m-2 m deep Soil Mo 1 m-2 m D SOILW_1_2 m_AvgDaily Avg Soil Moisture 1 m-2 m DAvg Sod Mo 1 m-2 m deep H TSOIL_0_0.1 mSoil Temp 0 cm-100 cm deep Soil T 0-100 cm D TSOlL_0_0.1 m_Avg Daily AvgSoil Temp 0 cm- DAvg Soil T 0-100 cm 100 cm deep H TSOIL_0.1_0.4 m SoilTemp 100 cm-400 cm deep Soil T 100 cm-400 cm D TSOIL_0.1_0.4 m_Avg DailyAvg Soil Temp 100 cm- DAvg Soil T 100 cm-400 cm 400 cm deep HTSOIl_0.4_1 m Soil Temp 400 cm-1 m deep Soil T 400 cm-1 m D TSOIL_0.4_1m_Avg Daily Avg Soil Temp 400 cm-1 m DAvg Soil T 400 cm-1 m deep HTSOIL_1_2 m Soil Temp 1 m-2 m deep Soil T 1 m-2 m D TSOIL_1_2 m_AvgDaily Avg Soil Temp 1 m-2 m DAvg Soil T 1 m-2 m deep SKY & SURFACE -HOURLY H TCDC_ALL Total Cloud Cover entire Cloud All atmosphere HTCDC_HIGH Total Cloud Cover highest level Cloud High H TCDC_LOW TotalCloud Cover lowest level Cloud Low H TCDC_MID Total Cloud Cover midlevel Cloud Mid H PRMSL Mean Sea Level Pressure MSLP H VIS VisibilityVis H DPT_2 m 2M Dew Point 2 m DP H RH_2 m 2M Relative Humidity 2 m RH HSPFH_2 m Specific Humidity Spec Hum H TMP_Hourly_2 m 2M Hourly Temp 2 mTHourly H TMP_Hourly_2 m_Chng_12 h 2M Hourly Temp 12 Hr Change 2 m hrT 12hr CHG H TMP_Hourly_2 m_Chng_18 h 2M Hourly Temp 18 Hr Change 2 m hr T18 hr CHG H TMP_Hourly_2 m_Chng_24 h 2M Hourly Temp 24 Hr Change 2 m hrT 24 hr CHG H TMP_Hourly_2 m_Chng_6 h 2M Hourly Temp 6 Hr Change 2 m hrT 6 hr CHG SKY & SURFACE DAILY D TMP_D_Avt_2 m 2M Daily Avg Temp 2 mDAvgT D TMP_D_Avg_2 m_Chng_6 h 2M Daily Avg Temp 6 Hr 2 m DAvgT 6 hr CHGChange D TMP_D_Avg_2 m_Chng_12 h 2M Daily Avg Temp 12 Hr 2 m DAvg T 12hr CHG Change D TMP_D_Avg_2 m_Chng_18 h 2M Daily Avg Temp 18 Hr 2 m DAvgT 18 hr CHG Change D TMP_D_Avg_2 m_Chng_24 h 2M Daily Avg Temp 24 Hr 2 mDAvg T 24 hr CHG Change D TMP_D_Avg_2 m_Diff_10 YAvg 2M Daily Avg Temp10 yr 2 m DAvg T 10 yr ANOM Anomaly D TMP_D_Avg_2 m_Diff_15 YAvg 2MDaily Avg Temp 15 yr 2 m DAvg T 15 yr ANOM Anomaly D TMP_D_Avg_2m_Diff_30 YAvg 2M Daily Avg Temp 30 yr 2 m DAvg T 30 yr ANOM Anomaly DTMP_D_Avg_2 m_Diff_o30 YCIimo 2M Daily Avg Temp 2 m DAvg T o30 yr ANOMOfficial30 yr Anomaly D TMP_D_MAX_2 m 2M Daily Max Temp 2 mD_XT DTMP_D_MAX_2 m_Chng_6 h 2M Daily Max Temp 6 Hr 2 mD_XT 6 hr CHG Change DTMP_D_MAX_2 m_Chng_12 h 2M Daily Max Temp 12 Hr 2 mD_XT 12 hr CHG ChangeD TMP_D_MAX_2 m_Chng_18 h 2M Daily Max Temp 18 Hr 2 mD_XT 18 hr CHGChange D TMP_D_MAX_2 m_Chng_24 h 2M Daily Max Temp 24 Hr 2 mD_XT 24 hrCHG Change D TMP_D_MAX_2 m_Diff_10 YAvg 2M Daily Max Temp 10 yr 2 mD_XT10 yr ANOM Anomaly D TMP_D_MAX_2 m_Diff_15 YAvg 2M Daily Max Temp 15 yr2 mD_XT 15 yr ANOM Anomaly D TMP_D_MAX_2 m_Diff_30 YAvg 2M Daily MaxTemp 30 yr 2 mD_XT 30 yr ANOM Anomaly D TMP_D_MAX_2 m_Diff_30 YCIimo 2MDaily Max Temp 2 mD_XT o30 yrANOM Official30 yr Anomaly D TMP_D_Min_2 m2M Daily Min Temp 2 mD_NT D TMP_D_Min_2 m_Chng_12 h 2M Daily Min Temp 12Hr 2 mD_NT 12 hrCHG Change D TMP_D_Min_2 m_Chng_18 h 2M Daily Min Temp18 Hr 2 mD_NT 18 hr CHG Change D TMP_D_Min_2 m_Chng_24 h 2M Daily MinTemp 24 Hr 2 mD_NT 24 hrCHG Change D TMP_D_Min_2 m_Chng_6 h 2M Daily MinTemp 6 Hr 2 mD_NT 6 hr CHG Change D TMP_D_Min_2 m_Diff_10 YAvg 2M DailyMin Temp 10 yr 2 mD_NT 10 yr ANOM Anomaly D TMP_D_Min_2 m_Diff_15 YAvg2M Daily Min Temp 15 yr 2 mD_NT 15 yr ANOM Anomaly D TMP_D_Min_2m_Diff_30 YAvg 2M Daily Min Temp 30 yr 2 mD_NT 30 yr ANOM homely DTMP_D_Min_2 m_Diff_30 YCIimo 2M Daily Min Temp 2 mD_NT o30 yANOMOfficial30 yr Anomaly DEGREE DAYS - DAILY D HDD Heating Degree Day 65degrees HDD D CDD Cooling Degree Day 65 degrees CDD Gas Weeks HDD_NG WksHeating Degree Day 65 degrees HDD NGwk (NGwk) Gas Weeks CDD NG WKsCooling Degree Day 65 degrees CDD NGwk (NGwh| D GWDD GWDD GWDD DGWDD_Chng_6 h GWDD 6 Hr Change GWDD 6 hr CHG D GWDD_Chng_12 h GWDD 12 HrChange GWDD 12 hr CHG D GWDD_Chng_18 h GWDD 18 Hr Change GWDD 18 hr CHGD GWDD_Chng_24 h GWDD 24 Hr Change GWDD 24 hr CHG D GWDD_Diff_10 YAvgGWDD 10 yr Anomaly GWDD 10 yr ANOM D GWDD_Diff_15 YAvg GWDD 15 yrAnomaly GWDD 15 yr ANOM D GWDD_Diff_30 YAvg GWDD 30 yr Anomaly GWDD 30yr ANOM D GWDD_Diff_o30 YAvgDlFF GWDD Official 30 yr Anomaly GWDD o30yrANOM Gas Weeks GWDD_NG WKs Gas Weighted Temp (NG weeks) GW Temp (NGwk)Gas Weeks GWDD_Chng Gas Weighted Temp 12 Hr GW T 12 hr CHG (NGwk) 6 h_NGWKs CHNG (NGwk) Gas Weeks GWDD_Chng Gas Weighted Temp 18 Hr GW T 18 hrCHG (NGwk) 12 h_NG WKs CHNG (NGwk) Gas Weeks GWDD_Chng Gas Weighted Temp24 Hr GW T 24 hr CHG (NGwk) 18 h_NG WKs CHNG (NGwk) Gas Weeks GWDD_ChngGas Weighted Temp 6 Hr CHNG GW T 6 hr CHG (NGwk) 24 h_NG WKs (NGwk) GasWeeks Gas Weighted Temp 10 yr GW T 10 yr ANOM (NGwk) GWDD_Diff_10YAvg_NG WKs Anomaly (NGwk) Gas Weeks Gas Weighted Temp 15 yr GW T 15 yrANOM (NGwk) GWDD_Diff_15 YAvg_NG WKs Anomaly (NGwk) Gas Weeks GasWeighted Temp 30 yr GW T 30 yr ANOM (NGwk) GWDD_Diff_30 YAvg_NG WKsAnomaly (NGwk) Gas Weeks Gas Weighted Temp Official GW T o30 yr ANOMGWDD_Diff_o30 YAvgDlFF_NG WKs 30 yr Anomaly (NGwk) (NGwk) D GWAvgT GasWeighted Daily Avg Temp GW Avg Temp D GWAvgT_Chng_12 h Gas Weighted AvgTamp 12 Hr GW AvgT 12 hr CHG CHNG D GWAvgT_Chng_18 h Gas Weighted AvgTamp 18 Hr GW AvgT 18 hr CHG CHNG D GWAvgT_Chng_24 h Gas Weighted AvgTemp 24 Hr GW AvgT 24 hr CHG CHNG D GWAvgT_Chng_6 h Gas Weighted AvgTemp 6 Hr GW AvgT 6 hr CHG CHNG D GWAvgT_Diff_10 YAvg Gas Weighted AvgTemp 10 yr GW AvgT 10 yr ANOM Anomaly D GWAvgT_Diff_15 YAvg Gas WeightedAvg Temp 15 yr GW AvgT 15 yr ANOM Anomaly D GWAvgT_Diff_30 YAvg GasWeighted Avg Tamp 30 yr GW AvgT 30 yr ANOM Anomaly D GW AvgT_Diff_o30VAvgDIFF Gas Weighted Avg Temp GW AvgT o30 yr ANOM Official 30 yrAnomaly Gas Weeks GWAvgT_NG WKs Gas Weighted Avg Temp (NG GW Avg Temp(NGwk) weeks) Gas Weeks Gas Weighted Avg Temp 12 Hr GW AvgT 12 hr CHGGWAvgT_Chng_12 h_NC WKs CHNG (NGwk) (NGwk) Gas Weeks Gas Weighted AvgTemp 18 Hr GW AvgT 18 hr CHG GWAvgT_Chng_18 h_NG WKs CHNG (NGwkl (NGwk)Gas Weeks Gas Weighted Avg Temp 24 Hr GW AvgT 24 hr CHG GWAvgT.Chng_24h.NG WKs CHNG (NGwk| (NGwk) GM Weeks GWAvgT Gas Weighted Avg Temp 6 HrGW AvgT 6 hr CHG Chng_6 h NG WKs CHNG (NGwk) (NGwk) Gas Weeks GasWeighted Avg Tamp 10 yr GW AvgT 10 yr ANOM GWAvgT_Diff_10 YAvg_NG WKsAnomaly (NGwb| (NGwk) Gas Weeks Gas Weighted Avg Temp 15 yr GW AvgT 15yr ANOM GWAvgT_Diff_15 YAvg_NG WKt Anomaly (NGwk) (NGwk) Gas Weeks GasWeighted Avg Temp 30 yr GW AvgT 30 yr ANOM GWAvgT_Diff_30 YAvg_NG WKtAnomaly (NGwk) INGwk) Gas Weeks Gas Weighted AvgTemp Official GW AvgTo30 yr ANOM GWAvgT_Diff_o30 YAvgDIFF_NG WKs 30 yr Anomaly (NGwk) (NGwk)D GWMaxT Gas Weighted Max Temp GW Max Temp D GWMaxT_Chng_12 h GasWeighted Max Temp 12 Hr GW XT 12 hr CHG CHNG D GWMaxT_Chng_18 h GasWeighted Max Temp 18 Hr GW XT 18 hr CHG CHNG D GWMaxT_Chng_24 h GasWeighted Max Temp 24 Hr GW XT 24 tM CHG CHNG D GWMaxT_Chng_6 h GasWeighted Max Temp 6 Hr GW XT 6 hr CHG CHNG D GWMaxT_Diff_10 YAvg GasWeighted Max Temp 10 yr GW XT 10 yr ANOM Anomaly D GWMaxT_Diff_15 YAvgGas Weighted Max Temp 15 yr GW XT 15 yr ANOM Anomaly D GWMaxT_Diff_30YAvg Gas Weighted Max Temp 30 yr GW XT 30 yr ANOM Anomaly DGWMaxT_Diff_o30 YAvgDIFF Gas Weighted Max Temp GW XT o30 yr ANOMOfficial 30 yr Anomaly Gas Weeks GWMaxT_NG WKs Gas Weighted Max Temp (NGGW Max Temp (NGwk) weeks) Gas Weeks Gas Weighted Max Temp 12 Hr GW XT 12hr CHG (NGwk) GWMaxT_Chng_12 h.NG WKs CHNG (NGwk) Gas Weeks Gas WeightedMax Temp 18 Hr GW XT 18 hr CHG (NGwk) GWMaxT_Chng18 h.NG WKs CHNG (NGwk)Gas Weeks Gas Weighted Max Temp 24 Hr GW XT 24 hr CHG (NGwk)GWMaxT_Chng_24 h.NG WKt CHNG (N6 wk) Gas Weeks Gas Weighted Max Temp 6Hr GW XT 6 hr CHG (NGwk) GWMaxT_Chng_6 h.NG WKs CHNG (NGwk) Gas WeeksGas Weighted Max Temp 10 yr GW XT 10 yr ANOM GWMaxT_Diff_10 YAvg_NG WKsAnomaly INGwk) (NGwk) Gas Weeks Gas Weighted Max Temp 15 yr GW XT 15 yrANOM GWMaxT_Diff_15 YAvg_NG WKs Anomaly (NGwk) INGwk) Gas Weeks GasWeighted Max Temp 30 yr GW XT 30 yr ANOM GWMaxT_Diff_30 YAvg_NG WKsAnomaly (NGwk) (NGwk) Gas Weeks Gas Weighted Max Temp GW XT o30 yr ANOMGWMaxT_Diff_o30 YAvgCLIMO_NG WKs Official 30 yr Anomaly (NGwk) (NGwk) DGWMinT Gas Weighted Min Temp GW Min Temp D GWMinT_Chng_12 h Gas WeightedMin Temp 12 Hr GW NT 12 hr CHG CHNG D GWMinT_Chng_18 h Gas Weighted MinTemp 18 Hr GW NT 18 hr CHG CHNG D GWMinT_Chng_24 h Gas Weighted Min Temp24 Hr GW NT 24 hr CHG CHNG D GWMinT_Chng_6 h Gas Weighted Min Temp 6 HrGW NT 6 hr CHG CHNG D GWMinT_Diff_10 YAvg Gas Weighted Min Temp 10 yr GWNT 10 yr ANOM Anomaly D GWMinT_Diff_15 YAvg Gas Weighted Min Temp 15 yrGW NT 15 yr ANOM Anomaly D GWMinT_Diff_30 YAvg Gas Weighted Min Temp 30yr GW NT 30 yr ANOM Anomaly D GWMinT_Diff_o30 YAvgDIFF Gas Weighted MinTemp GW NT o30 yr ANOM Official 30 yr Anomaly Gas Weeks GWMinT_NG WKsGas Weighted Min Temp (NG GW Min Temp (NGwk) weeks) Gas Weeks GasWeighted Min Temp 12 Hr GW NT 12 hr CHG (NGwk) GWMinT_Chng_12 h_NG WKsCHNG (NGwk) Gas Weeks Gas Weighted Min Temp 18 Hr GW NT 18 hr CHG (NGwk)GWMinT_Chng_18 h_NG WKs CHNG (NGwk) Gas Weeks Gas Weighted Min Temp 24Hr GW NT 24 hr CHG (NGwk) GWMinT_Chng_24 h_NG WKs CHNG (NGwk) Gas WeeksGas Weighted Min Temp 6 Hr GW NT 6 hr CHG (NGwk) GWMinT_Chng_6 h_NG WKsCHNG (NGwk) Gas Weeks Gas Weighted Min Temp 10 yr GW NT 10 yr ANOMGWMinT_Diff_10 YAvg_NG WKs Anomaly (NGwk) (NGwk) Gas Weeks Gas WeightedMin Temp 15 yr GW NT 15 yr ANOM GWMinT_Diff_15 YAvg_NG WKs Anomaly(NGwk) (NGwk) Gas Weeks Gas Weighted Min Tamp 30 yr GW NT 30 yr ANOMGWMinT_Diff_30 YAvg_NG WKs Anomaly (NGwk) (NGwk) Gas Weeks Gas WeightedMin Temp GW NT o30 yr ANOM GWMinT_o30AvgDlFF_NG WKs Official 30 yrAnomaly (NGwk) [NGwk)

Components of DID system 102 (FIG. 1 ) and/or weather integration server116 (FIG. 2 ) of the present disclosure may be embodied on a singlecomputing device. In other examples, components of DID system 102 and/orweather integration server 116 may be embodied on two or more computingdevices distributed over several physical locations, connected by one ormore wired and/or wireless links. It should be understood that DIDsystem 102 of the present disclosure refers to a computing system havingsufficient processing and memory capabilities to perform the specializedfunctions described herein.

Some portions of the present disclosure describe embodiments in terms ofalgorithms and/or routines and symbolic representations of operations oninformation. These algorithmic descriptions and representations are usedto convey the substance of this disclosure effectively to others skilledin the art. These operations, while described functionally,computationally, or logically, are to be understood as being implementedby data structures, computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, at times, it may be convenient torefer to these arrangements of operations as routines or algorithms. Thedescribed operations and their routines/algorithms may be embodied inspecialized software, firmware, specially-configured hardware or anycombinations thereof.

Those skilled in the art will appreciate that DID system 102 (of FIG. 1) may be configured with more or less components to conduct the methodsdescribed herein with reference to FIGS. 3A and 3B. The methodsdescribed herein (that may be conducted by DID system 102 of the presentdisclosure) may be performed by processing logic that may comprisehardware (e.g., circuitry, dedicated logic, programmable logic,microcode, etc.), software (such as instructions run on a processingdevice), or a combination thereof. In one embodiment, the methodsdescribed herein may be performed by one or more specialized processingcomponents associated with components 204-216 of weather integrationserver 116 of FIG. 2 . With respect to FIGS. 3A and 3B, although theseflowcharts may illustrate a specific order of method steps, it isunderstood that the illustrated methods are exemplary, and that theorder of these steps may differ. Also, in some examples, two or moresteps may be performed concurrently or with partial concurrence.

FIG. 3A is a flowchart diagram of an example method 300 of generatingintegrated weather and market data associated with data distributionenvironment 100 of FIG. 1 , and weather integration server 116 and timeseries server 118 of FIG. 2 , according to an aspect of the presentdisclosure.

At step 302, weather integration server 116 may store a pre-definedweather symbology (e.g., in storage 214). The weather symbology mayinclude one or more pre-defined symbol elements, one or more variablesand one or more pre-defined rules for combining and/or arrangingelements among the symbol elements to form a weather symbologyinstruction having a pre-defined instruction structure. As discussedherein, the inclusion of one or more symbol elements in the pre-definedinstruction structure may be used to create a variety of weathersymbology instructions. In general, a weather symbology instruction mayinclude symbol elements including at least one weather observationlocation, a weather structure (such as a weather perspective) andweather forecast model information. The weather symbology instructionmay include additional variable information (such as condition(s) and/orfunction(s)) for generating desired weather forecast/observations datathat may be integrated with market data, and that may provide actionableknowledge. In some examples, the symbol elements may be linked todifferent segments of weather data stream(s) associated with weatherdata source(s) 104.

At step 304, data collector 112 may collect weather data among weatherdata source(s) 104. In some examples, the weather data may includeweather observations data for one or more observation locations andweather forecast model data for one or more weather forecast models(including, in some examples, different model runs). At step 306, datacollector 112 may collect market data among market data source(s) 106.In some examples, collected weather data (step 304) may be distributedto weather integration server 116 and collected market data (step 306)may be distributed to time series server 118 (e.g., by data feeddistributor 114). In some examples, weather integration server 116 maysegment the collected weather data (step 304) into one or more segmentsbased on the weather symbology (stored in step 302). It is understoodthat both the weather data and the market data may change over time andthat steps 304 and 306 may include repeatedly collecting the weather andmarket data respectively, as the corresponding data changes. It is alsounderstood that updates to the weather data may occur at differentfrequencies than updates to the market data. In some examples, thecollection of weather and market data (steps 304 and 306) may includethe capture of (real-time) weather data stream(s) and (real-time) marketdata stream(s) (e.g., via one or more data feeds).

At step 308, DID system 102 may generate interactive GUI 120 includingweather impact dashboard 122 for display on user device(s) 108. In someexamples, a configuration of weather impact dashboard 122 may depend onan underlying client application/service 126 for which it is launched(e.g., a trading desktop, a mobile application, a spreadsheetapplication, an API, etc.). At step 310, time series server 118 mayreceive a weather data request (e.g., data request 224) from userdevice(s) 108 via interactive GUI 120.

At step 312, time series server 118 may determine a weather symbologyinstruction based on the received weather data request (step 310). Insome examples, the weather data request may directly include the weathersymbology instruction. In some examples, time series server 118 mayconvert the weather data request into the weather symbology instructionhaving the pre-defined instruction structure, in accordance with thepre-defined rules and pre-defined symbology elements (step 302) storedin storage 214.

At step 314, time series server 118 may determine a pre-defined weatherstructure (e.g., a perspective) from the weather symbology instruction(determined in step 312). At step 316, time series server 118 may createa weather forecast (and/or observations) dataset (also referred to asweather forecast/observations dataset) from among the collected weatherdata, based on the weather symbology instruction including the weatherstructure indicated in the weather symbology instruction. For example,time series server 118 may obtain the corresponding weather perspectiveamong the weather structure(s) (from storage 216), and may extract atleast a portion of the segmented weather data 218 (from among thecollected observation data and at least a portion of the weatherforecast model data) based on the symbol elements/variable(s) in theweather symbology instruction. The extracted weatherforecast/observation(s) data associated with the weather symbologyinstruction and any other data and/or information associated with thecorresponding weather structure may then form the weatherforecast/observations dataset. The weather forecast/observations datasetmay also be formed as a function of exchange time and interval time, forease of integration with the collected market data.

At step 318, time series server 118 may generate an integratedpresentation package comprising a combination of the weatherforecast/observations dataset (step 316) and a portion of the collectedmarket data (step 306), configured in such a manner so that the weatherforecast/observations dataset is integrated with the portion of thecollected market data. At step 320, the integrated presentation package(step 318) may be presented on interactive GUI 120 via weather impactdashboard 122. In some examples, the integrated presentation package maybe presented in such a manner to permit user interaction, including, insome examples, user-customization of the integrated presentationpackage. At optional step 322, DID system 102 may expose the integratedpresentation package to one or more APIs. In some examples, step 320 maynot be performed and step 322 may be performed instead. In someexamples, steps 308 may not be performed and step 310 may includereceiving a weather data request via user device(s) 108, without beingreceived via an interactive GUI (e.g., via clientapplication(s)/service(s) 126).

At step 324, the integrated presentation package may be updated (e.g.,on weather impact dashboard 122, via one or more APIs) concurrent withchanges to the weather data, the market data and/or user input(including changes in real-time). In some examples, the weather andmarket data may each include real-time data streams, such that steps 318and 320 (and/or optional step 322) may generate and present thepresentation package in real-time, using real-time streaming data.

FIG. 3B is a flowchart diagram of an example method 330 of generatingintegrated weather and market data for streaming data associated withdata distribution environment 100 of FIG. 1 , and weather integrationserver 116 and time series server 118 of FIG. 2 , according to an aspectof the present disclosure.

At step 332, a pre-defined weather symbology may be stored, for example,in storage 214. As described herein, the weather symbology may includepre-defined symbol elements that may be linked to one or more segmentsof one or more weather data streams. In some examples, storage 214 mayalso store one or more rules for generating weather symbologyinstruction(s). In some examples, DID system 102 may include apre-defined market symbology, similar to the weather symbology, that maybe linked to one or more segments of one or more market data streams.

At step 334, one or more data feeds to weather data source(s) 104 andmarket data source(s) 106 may be initiated, for example, via datacollector 112. In example method 330, weather data source(s) 104 andmarket data source(s) 106 may provide streaming data via correspondingdata feed(s). In some examples, data collector 112 may also receiveother data/information from among weather data source(s) 104 and marketdata source(s) 106 in a non-streaming manner, such as, periodically, inresponse to an event, condition and the like. At step 336, datacollector 112 may receive one or more weather data streams from weatherdata source(s) 104 (via respective data feed(s) initiated in step 334).At step 338, data collector 112 may receive one or more market datastreams from market data source(s) 106 (via respective data feed(s)initiated in step 334).

At step 340, the received weather data stream(s) (in step 336) may besegmented (e.g., separated and/or indexed), for example, by weatherintegration server 116, based on the weather symbology (stored in step332), to form segmented (streaming) weather data. For example, theweather data stream(s) may be segmented in accordance with the (linked)pre-defined symbol elements. In this manner, a particular segment of thesegmented weather data that is linked to a particular pre-defined symbolelement may be extracted and the extracted (streaming) segment used tocreate an integrated presentation package, stream to user device(s) 108,provided to an external system for further analysis and the like. Insome examples, time series server 118 may be configured to segment thereceived market data stream(s) into one or more segments based on apre-defined market symbology.

At step 342, time series server 118 may receive a weather data request(e.g., via interactive GUI 120, via client application(s)/service(s)126, etc.). At step 344, time series server 118 may identify one or morerequested symbol elements (and in some examples, one or more variables)in the received weather data request (step 344). At step 346, timeseries server 118 may create at least one weather symbology instructionbased on the identified symbol element(s) (and, in some examples anyvariables) as identified in step 344. In some examples, the receivedweather data request (step 342) may directly include in a weathersymbology instruction, so that steps 344 and 346 may be skipped.

At step 348, time series server 118 may extract one or more segments ofthe segmented weather data stream(s) according to the weather symbologyinstruction (step 346) to form one or more extracted weather stream(s)associated with the weather symbology instruction. In particular, theidentified symbol elements, that are linked to corresponding segments ofthe segmented weather data stream(s) may be used to extract particularsegment(s) of the segmented weather data stream(s). In some examples,any variables (e.g., conditions, functions) in the weather symbologyinstruction may be used to further extract segment(s) and/or portion(s)of segment(s) of the segmented weather data stream(s).

At step 350, time series server 118 may create a real-time (streaming)weather dataset from the extracted weather stream(s), based on theweather data request (step 342). More particularly, a weather structurethat may be indicated in the weather symbology instruction (determinedfrom the weather data request) may be obtained from storage 216, and maybe used to create the real-time weather dataset from the extractedweather stream(s). The real-time weather dataset may be formed as afunction of exchange time and interval time, for ease of integrationwith the market data stream(s).

At step 352, time series server 118 may generate an integratedpresentation package of the real-time weather dataset and one or moremarket data stream(s) (received at step 338). In some examples, timeseries server 118 may also extract one or more segments among similarlysegmented market data stream(s) based on any market data symbology(e.g., indicated in the weather data request, based on pre-definedparameter(s) set by DID system 102, based on pre-defined parameter(s)indicated by the user, and the like).

At step 354. DID system 102 may expose the integrated presentationpackage to one or more APIs. At optional step 356, the integratedpresentation package may be presented on weather impact dashboard ofinteractive GUI 120. In some examples, step 354 may not be performed andstep 356 may be performed instead. In some examples, both steps 354 and356 may be performed.

At step 358, the integrated presentation package may be updated (e.g.,via one or more APIs, on weather impact dashboard 122, etc.) concurrentwith changes to the weather data stream(s), the market data steam(s)and/or user input.

Referring to FIG. 3C, hierarchical diagram 360 illustrating exampleweather symbology 362 and use of weather symbology 362 to form variouspresentation packages 370 are shown. In general, weather symbology 362may include one or more weather symbol elements 364 (e.g., weather modelsources, weather model locations and weather functions also referred toas weather perspectives). Weather symbology 362 may also include one ormore weather variables 366 (e.g., functions and/or conditions). Symbolelement(s) 364 and weather variable(s) 366 may be linked to particularsegments of one or more weather data streams. A combination of symbolelement(s) 364 and weather variable(s) 366 may be arranged into at leastone weather symbology instruction (having the instruction structuredescribed herein) in order to extract the particular linked segments ofthe weather data stream(s) to form a weather dataset. Similarly, timeseries server 118 may use market data symbology 368 (symbolelements/variables associated with, for example, commodity prices,supply/demand data, equity prices, earning per share data, fixed incomedata, municipal bonds, etc.) to extract particular segments from marketdata stream(s). Time series server 118 may combine the weather dataset(from among weather symbology 362 and market data symbology 368) to formone or more presentation packages 370 (e.g., charts, watchlists, tables,grids, alerts, data feeds, data associated with object orientedprogramming languages (e.g., Python™), spreadsheet-formatted data (suchas with RTD links), etc.). Presentation package(s) 370 may be presentedto user device(s) 108 via client application(s) service(s) 126. In someexamples, presentation packages(s) 370 may be further configured intoone or more weather workbooks 372 (e.g., natural gas (North America(NA), Europe (EU)), power, global crude oil, etc.) for presentation ontrade desktop 374.

In general, weather symbology 362 may be configured to instantly convertweather data into accurate and actionable knowledge, tailoredspecifically for traded instruments, via one or more (interactive)presentation packages. In some examples, weather data may be accessed inreal-time suing weather symbology 362. Because of the weather symbologyof the present disclosure, extremely large streams of weather and pricedata may be converted into Actionable Knowledge (such as presentationpackages 370, weather workbooks 372 and the like). Of significance,weather symbology 362 provides a mechanism to rapidly break downstreaming weather data into the smallest possible building blocks in amanner configured to be integrated with market data handled by timeseries server 118, and for interactive presentation on trading desktop374. The actionable knowledge (e.g., components 370, 372) created by DIDsystem 102 allows users to instantly and easily interact with bothweather and price data streams (e.g., including through time and space).Still further, weather symbology 362 allows user to create anyuser-customizable weather display. In some examples, weather symbology362 may be configured to treat weather data similar to a tradedinstrument, so that weather symbol element 364/weather variable 366 maybe entered directly into a chart, table, watchlist, etc. to view theweather data directly. Yet further, weather symbology 362 also allow theweather data to be accessed from multiple directions (e.g., threeseparate directions, catering to (in some examples) three primaryweather workflows (e.g., guidance, progression and accuracy).

Description of Weather Symbology

Next, a detailed description of the weather symbology of the presentdisclosure is provided.

-   -   1) General: All symbols (also referred to as symbol elements)        have the same basic structure. In general, a weather symbology        instruction includes a same pre-defined weather symbology        instruction structure:        -   a. Location {space} Function {underscore}_ Model Run {Dash}-            Wx Model. {dot} field name            -   i. EX: KORD MR0!_12 z-GFS            -   ii. wx variables can be added at the end of the weather                symbol            -   iii. ‘Model Run’ is an optional field            -   iv. Dates are expressed as YYMMDD (2 digits each)                -   1. If a specific hour of the day (or model hour) is                    required, it accepts 1-3 digits:                -    a. YYMMDDHHH            -   v. Model runs (2 digits along with a “z”, for example                06z)            -   vi. Rolling Symbols have a bang “!”    -   2) Guidance (aka Model Runs): All weather symbols below can        access any time aggregations such as seasonal, monthly, weekly        and as an example both “Daily” weather forecast fields (e.g.,        days 1-16) or “Hourly” weather forecasts (e.g., model hours        1-384). See FIG. 5 .        -   a. ROLLING            -   i. KORD MR0! (Model Run Now) is the current model                (whatever wx model is running now, or the last model to                run (if in between model runs). This instruction                extracts the latest weather model which is coming in now                or the last model to have run.                -   1. EX: KORD MR0!-GFS            -   ii. KORD MR0!_12 z-GFS is requesting the latest 12z                model run.                -   1. To access any previous model run of the 12z see                    below. If the 12z was omitted the symbol would                    return the last run of the GFS, whichever model run                    was the most current.            -   iii. MR1! (1 through 99) is that many “model runs ago”                for whatever comes after it. Will go back x # of runs                for the suffix. So MR1!_12x-GFS will be yesterday's 12z                GFS, MR1! GFS will be 1 model run ago.                -   1. KORD MR1!-GFS (for −1 model run back, from which                    ever model run of the GFS is current)                -   2. KORD MR1!_12 z-GFS (for the previous days run of                    the specific 12z GFS)        -   b. Specific            -   i. Daily                -   1. KORD MR200301-GFS (YY,MM,DD): returns all the GFS                    weather forecast model runs which were produced on                    Mar. 1, 2020 (aka Model Run Date) This function                    provides extraction of a historical weather forecast                    from specific “model run dates” and for specific                    weather models and model runs.            -   ii. Model Run Specific                -   1. KORD MR200301_12 z-GFS (YY,MM,DD): returns only                    the 1 model run (i.e. 12z) of the GFS which was                    produced on Mar. 1, 2020 and is the 12z. This                    function provides extraction of a historical weather                    forecast from specific “model run dates” and for                    specific weather models and runs.    -   3) Progression (aka Forecast Dated Day & Forecast Dated Hour):        Provides an analysis of how the forecast models changed over        time for a specific Forecast Valid ‘Day’, ‘Date’ or ‘time of        day’ (aka hour) on a specific Date also known as the “Target        Date. Can be displayed in “Exchange time” or “interval start”).        Note: when charting these symbols it may be useful to ‘chart’        using “exchange time” (on the x axis) to view this progression        data in the correct order (i.e. as it was released by model        run), considering the Forecast Valid ‘day/date’ is locked into        the symbol (i.e. the Forecast Valid data is normally plotted on        the x axis using local day/date. See FIGS. 6A-6C.        -   a. Specific:            -   i. Daily Forecast: KORD FDD200301_12 z-GFS (YY,MM,DD):                This symbol provides a history of all the 12z GFS                weather forecasts, which pertain to that specific target                ‘Date’ which is noted in the symbol; e.g., Mar. 1, 2020.                Note: If the “12z” was omitted in this symbol, the                alternate symbol design would return “all model runs” of                the GFS, which provided a (daily) forecast for that                specific date.            -   ii. Hourly Forecast: KORD FDH20030113_12 z-GFS                (YY,MM,DD,HH): Same as above, but provides a specific                hour (aka time of day) on a specific date. This symbol                provides a history of all the 12z GFS Forecasts and may                return the weather forecasts which pertain to that                specific ‘Date’, e.g., Mar. 1, 2020 at 1 pm “local time”                for that specific location. In an example, this specific                “time of day” is noted by hour “13”, which is appended                to the date. The “13” represents the “local time” of                day, for that specific location. The last 2 digits range                from 01 (1 am) to 24 (midnight). Note: If the “12z” was                omitted in this symbol, the new symbol would return “all                model runs” of the GFS, which provided an “Hourly”                forecast for that time of day, for that specific date.        -   b. Rolling            -   i. Daily Forecast: KORD FDD2!-12z-GFS: This symbol acts                exactly in the same manner as above, except that the                specific “Date” may be unknown (just the Forecast Valid                “Day” may be known). For example if a user did not know                tomorrow's “Date” this rolling symbology structure may                be used to lock into the “Date” which is now “Day2”.                -   1. In summary: This symbol provides a history of all                    the 12z GFS weather forecasts, which pertain to that                    specific target “Date” which is now noted in the                    symbol; as “Day2”. Tomorrow that same “Day2” element                    in the weather symbol, will refer to a different                    specific “Forecast valid Date”.                -   2. Note: If the “12z” was omitted in this symbol,                    the new symbol would return “all 4 model runs” of                    the GFS, which provided a daily forecast for that                    specific ‘Date’, which is currently Day 2.                -   3. Note because “Day 1” equals “Today”. That is                    different than the manner in which we normally                    count. For example, FDD7! is 6 days from today.            -   ii. Hourly Forecast: KORD FDD2_H13!-12z-GFS: Provides a                history of all the 12z Forecasts and may return the                weather forecasts which pertain to that specific                “Forecast Day” at that specific “Time of Day” on                tomorrow Day 2, being “Local Hour 13” which is 1 pm.                Note: These times are expressed as the local hour of the                specific location's day/date.                -   1. If the “12z” was omitted in this symbol, the new                    symbol would return “all 4model runs” of the GFS,                    which provided a Hourly forecast for that specific                    date & time which is currently defined as Model Hour                    120.                -   2. Note the H is two (2) digits ranging from 1-24,                    with 1=lam and 24=midnight.            -   iii. Model Hour: KORD FDH012z-GFS: Returns the history                of 12z GFS weather forecasts for only model hour 0. This                is independent of what every the local day/time is                related to the forecast Valid period (acting very                similar to an accuracy workflow like the KORD FCH13!_12                z-GFS example (below).                -   1. If the “12z” was omitted in this symbol, the new                    symbol would return “all 4model runs” of the GFS,                    which provided a Hourly forecast for Model Hour 0.                -   2. Note that H is two (2) digits ranging from 0-384.    -   4) Accuracy (aka Forecast Continuation Day & Forecast        Continuation Hour): This symbology structure may line up the        weather forecast data in a manner which allows a user to easily        match the extracted weather forecasts with weather observations.        These observations can then be subtracted from the extracted        forecasts to derive forecast accuracy statistics such as Bias,        root mean square error (RMSE), Error, standard deviation (std)        of error, etc. In summary, this Accuracy based symbology may        return all historical weather forecast information in a manner        which lines up all previous weather forecasts for a specific        (rolling) days in the future (like all the ‘Day 1’ forecasts        would be lined up (then all day 2, 3, 4, etc.) or specific        (rolling) “model hours” in the future (like model hour 3, 6, 9,        12, etc.) See FIGS. 7A and 7B.        -   a. Rolling            -   i. Daily Forecast: KORD FCD1!_12 z-GFS: Provides the                “Day 1” forecast from all 12z GFS weather forecasts                stored in a database.                -   1. Note: If the “12z” was omitted in this symbol,                    the new symbol would return “all 4 model runs” of                    the GFS.            -   ii. Hourly Forecast: KORD FCH13!_12 z-GFS: Provides the                “model hour 13” forecast from all 12z GFS weather                forecasts stored in a database. Note: These are forecast                “model hours” and range from 0-384 as opposed to the                manner in which “Forecast Valid” date & time of day is                used (as in FDH above) which starts at ‘1’ indicating                lam local time, for a specific location.                -   1. Note: If the “12z” was omitted in this symbol,                    the new symbol would return “all 4model runs” of the                    GFS.    -   5) METAR SYMBOLOGY: METAR is one particular source of global        weather observations. METAR reports weather observations from        key airports (globally) in a relatively timely manner, so there        is typically little (if any) cleaning to this weather        observation data stream.    -   a. General Structure <Location><Suffix>        -   i. KORD-METR    -   6) MISCELLANEOUS (MISC.):        -   a. AutoListing: save the user time from typing in many            different symbols.            -   i. MR's                -   1. *<Location>MR!<Model>—returns 4 current model                    runs                -   2. Example: *KORD MR!-GFS                -   3. *<Location>MR!<Model><N-N>—returns the last N                    Model Runs                -   4. Example: *KORD MR!_12z-GFS 0-2            -   ii. FDD's (Progression)                -   1. *<Location>FDD!<Model>−returns FDD 1-16                -   2. Example: *KORD FDD!_12z-GFS                -   3. *<Location>FDD!<Model><N-N>—returns the last N                    FDD                -   4. Example: *KORD FDD!_12z-GFS 1-5                -   5. *<Location>FDH!<Model>—returns all hourly symbols                -   6. Example: *KORD FDH!_12 z                -   7. *<Location>FDH!<Model><N-N>—returns N hourly                    symbols                -   8. Example: *KORD FDH!_12 z 1-12            -   iii. FC's (Accuracy)                -   1. *<Location>FCD!<Model>—returns all continuous                    daily history symbols                -   2. Example: *KORD FCD!_12z                -   3. *<Location>FCD!<Model><N-N>—returns N continuous                    daily history                -   4. Example: *KORD FCD!_12z 1-12        -   b. Forecast Valid Days: 1-16 (or beyond, depending upon the            duration of the various wx forecast models): Day 1=today            (there is no Day 0). In some examples, “Day 1=today”, so            “Forecast Valid Day 4” is “3 days” from now (For            example: (1) today/Monday, (2) tomorrow/Tuesday, (3) next            day/Wednesday, (4) target day/Thursday).        -   c. Model Runs (00z-23z). Most Weather Forecast Models are            00z, 06z, 12z, 18z)        -   d. Forecast Valid Hours in a Specific ‘Date’ or ‘Day’ (e.g.,            in local time)            -   i. Range from 1-24 (e.g., 13=1:00 pm local time)        -   e. Forecast ‘Model Hours’, in some examples, may be from the            start of the weather model run and extend out into the            future. In some examples, weather forecast models are 384 or            240 hours into the future.            -   i. Range from 0-384 (for example).        -   f. Ensemble Variables            -   i. Location_ {underscore} Ensemble variable {space}                Function _ {underscore} Model Run {Dash}- Wx Model                -   1. EX: KORD MEAN MR0!_12z-GFS            -   ii. In some examples, a default variable for Ensemble                models is the “MEAN” or average of all perturbations            -   iii. Other selectable Ensemble variables may include:                -   1. MAX (highest ensemble member)                -   2. MIN (lowest ensemble member)                -   3. MEAN (Average of all ensemble members or also can                    be used as 50% of all members)                -   4. +1/−1 STD (1 standard deviation is derived which                    can be added or subtract from the MEAN)                -   5. PER10 (10^(th) percentile of all members)                -   6. PER25 (25^(th) percentile of all members)                -   7. PER75 (75^(th) percentile of all members)                -   8. PER90 (90^(th) percentile of all members)            -   iv. GFS ENS: Fast vs Full—                -   1. Fast may be derived using, for example, 50% of                    the total Ensemble members. For example, the first                    10, of the 20 ensemble members. These preliminary                    values have an extraordinarily high correlation to                    capture the directional change (and magnitude) of                    the Full forecast. The benefit to providing this                    directional perspective is receiving this                    information approximately 30 seconds before all                    ensemble members can be modeled and transmitted to                    other users. This concept works for streaming                    Ensemble models (e.g., GFS ENS), when ALL Ensemble                    members are computed.            -   v. Interpolated Values:                -   1. In some examples systems of the present                    disclosure may receive weather forecasts (which may                    arrive “As-Is”), and interpolate the forecast hours                    which were not forecasted by the weather model. In                    some examples, systems of the present disclosure may                    extract the “Trailing Minimum” and “Trailing                    Maximum” temperatures from the weather forecast grib                    files, and then using a diurnal pattern based upon                    data (or a blend of data), may place these trailing                    Minimum & Maximum values between the reported                    forecasts which reside on the top of each hour.            -   vi. % Complete:                -   1. This is a unique element of the present                    disclosure which allows users an advantage, viewing                    official daily weather forecast information a few                    minutes prior to the rest of the marketplace. This                    process may provide “preliminary forecasted values”                    for daily Max, Min, Avg temperature, or daily GWDD,                    Heating Degree Day (HDD), Cooling Degree Day (CDD)                    values, when the weather forecast model is partially                    (e.g., 50%) completed for any forecast Day and                    provide real-time updates as that forecast Day runs                    through 100% complete. The preliminary Daily values                    of the present disclosure may provide users insight,                    a few minutes in advance of other services, who only                    publish a forecast Day at 100%.

FIGS. 8A and 8B provide for specific operational examples of how thevarious weather symbology structures operate using sample weatherforecasts. For example, FIG. 8A illustrates example interactive GUI 800of a spreadsheet application, illustrating examples symbologyconstruction, according to an aspect of the present disclosure. FIG. 8Billustrates example interactive GUI 810 illustrating examples of variousweather symbology structures for a spreadsheet application.

Table 3 provides brief descriptions of example weather terminology usedthroughout the present disclosure.

TABLE 3 Example Weather Symbology Terminology Term Description ReceiptTime (e.g., The time reported is the time at which the file arrived atthe server(s). exchange time) Location Locations may be global airportcodes (ICAO) and/or custom regions designed to represent specificgeographic regions related to a specific commodity (such as a gasweighted Energy Information Administration (EIA) region-based commodityor one or more Independent System Operator (ISO) regions to mimic anentity that controls and monitors the operation of an electrical powersystem for a given geographic region). Example Weather GFS- GFS (¼degree spatial resolution. Time steps: mhr 0-120 @1 hr; Models/Model mhr121-384 @3 hr - run 4x per day). Names GEFS - GFS Ensemble (¼ degreespatial resolution. Time steps: mhr 0- 120 @1 hr - mhr 121-384 @3 hr.run 4x per day. Fast = 17 members/ Full = 35 members. ECM- ECMWF's highresolution model (¼ degree spatial resolution for surface variables and1 degree resolution for upper air variables. Time steps: mhr 0--90@1hr_mhr 93-144 @3 hr_mhr 150-240 @6 hr_0z & 12z ONLY. 06 & 18z mhr 0-90 @1 hr. ECE - ECMWF Ensemble model (ENS) (½ degree spatial resolution forsurface variables and 1 degree resolution for upper air variables. Timesteps: mhr 0--90@1 hr_mhr 93-144 @3 hr_mhr 150-240 @6 hr_0z & 12z ONLY.06 & 18z mhr 0-90 @ 1 hr_mhr 93-144@3 hr. Full = 52 members. ECEX- ECMWFEnsemble Extension (ENS) (½ degree spatial resolution for surfacevariables and 1 degree resolution for upper air variables. Time steps:mhr 0--384 @24 hr - run 2x per week). GEFSX - GFS Ensemble EXTENSION (¼degree spatial resolution. Time steps: mhr 0-120 @1 hr - mhr 121-384 @3hr. run 1x per day. Fast = 11 members/Full = 22 members. CFSX - CFSEnsemble EXTENSION (¼ degree spatial resolution. Time steps: mhr 0-5,400(9 mo) @6 hr -. run 1x per day. Full = 5 members. SEAS - ECMWF”sSeasonal Model (¼ degree spatial resolution. Time steps: mhr 0-5,040 (7mo) @6 hr -. run 5th of every month. Full = 5 members. Note that thespatial resolution is subject to change based upon the sources. ModelRun Currently 0z, 6z, 12z, 18z. This may change depending uponmodification by weather agencies to modify the frequency of model runs.Model Hour (aka Currently integers between 0-384. 0 hour is the initialhour from which Forecast Hour) the weather forecast is initialized andthe model physics then prognosticates forward into the future. TimeSteps/ Is the difference between Model Hours described above. Forexample if Reporting interval the forecasted model hours were 0, 3, 6,9, 12, etc., the model would possess ‘3 hour’ time steps. Forecast ValidA particular time for which a weather forecast will pertain to acalendar Date ‘Date’. Dates are based upon midnight-to-midnight localtime of the forecasted location. “FV Dates” are mostly used in “SpecificDates” for the weather symbology structure. Forecast Valid A particulartime for which a weather forecast will pertain to a calendar Day ‘Day’in the future, which is based upon midnight-to-midnight local time ofthe forecasted location. Mostly used in “Rolling Dates” for the weathersymbology structure. For example; Day 2 represents a forecast fortomorrow, regardless of which specific calendar date it represents.Forecast Valid A particular weather forecast for a particular time ofDay or Date, which Hour (Time of is based upon midnight-to-midnightlocal time of the forecasted location. Day) This Forecast Valid Hour canbe applied in either “specific” or rolling” weather symbology structure.For example; HH01 is 1:00am in the morning, local time. How Model HourEach Model Hour provides a global forecast which may correspond to arelates to Forecast specific Forecast Valid Day, Date and Time, giventhe global time zone Valid Day/FV of the specific forecast location. Forexample, Model Hour 1 may be Date/FV Time of equal to 1am London time,but may directly correspond to 7pm Chicago Day time (which is 6 hrsbehind London). (these are FV Day = Day 1, 2, 3, etc . . . expressed inlocal FV Date = a specific calendar date time for the FV Time of Day = aspecific time on a specific Date forecast location) Percent Complete AKA“Preliminary Daily Values” provides users an early view of what theforecasted daily value will (likely) be a few minutes in advance.Percent Complete displays the percentage of potential hourly data usedto derive a daily value for a specific forecast date/day. For example,the second forecast day (for some location) consists of 24 forecasthours. When 12 of those 24 files are received, a preliminary daily valuemay be generated for that specific day, As each subsequent forecast hourupdates from the forecast model, so will the % complete, unit 100% isachieved for that specific forecast day. “As-Is” model This refers tothe specific model hours in which a weather forecast model data (aka“Raw” provides a forecast. model data) Interpolated This refers to theforecast hours in between the “As-Is model data” from which the weatherforecast model did not provide weather forecast data. The presentdisclosure implements a sophisticated method to interpolate those inbetween hours. Blended Indicates whether a weather forecast data iscombined with observation data. Ensemble Models Ensemble runs mayproduce eight (8) distinct outputs regarding ensemble statistics for agiven variable. Max - The highest ensemble member Min - The lowestensemble member Mean - The average of all ensemble members. Std - 1standard deviation of all the ensemble members. 10% - - 10^(th)percentile of the ensemble values. 25% - - 25^(th) percentile of theensemble values. 50% - - 50^(th) percentile of the ensemble values canbe displayed by using the “Mean” (listed above). 75% - - 75^(th)percentile of the ensemble values. 90% - - 90^(th) percentile of theensemble values. Ensemble Member This is how many ensemble members areincluded in the analysis. For Count GEFS ‘Fast’, an early look at theensemble data may be provided using a portion (e.g., 22) of the total(e.g., 45) GEFS ensemble members. Guidance Charts Plot weather forecastsgoing out into the future (standard weather charts) Progression ChartsMay “lock” a particular “Forecast Valid Date or Time of Day” (also knownas the “Target Date”) and show how the previous weather forecasts havechanged over time for that “Forecast Valid” Day, Date or Time of Day.Target Date Used in a progression chart it is the specific Date and/orTime of Day which is held constant from which an examination of how allthe previous weather forecast Models/Model Runs have changed (overtime)for that particular Day/Date/Time. Alpha Charts This is the uniquedisplay in the marketplace and exclusive to aspects of the presentdisclosure. Streaming weather forecasts as they are made available intothe public domain in conjunction with real-time market prices, can moreeasily expose the relationship between changing weather perspectives andchanges in traded instruments. NOAA National Oceanic and AtmosphericAdministration www.noaa.gov NCEP National Center for Environmentalprediction www.ncep.noaa.gov ECMWF European Center of Medium RangeWeather Forecasts www.ecmwf.int CFSR A source of global weatherobservations. The Re-Analysis data from the CFS weather forecast modelmay be used to compile, in some examples, greater than 41 analog yearsand at least four climatological datasets. METAR A source of streamingglobal weather observations from instrumentation located at airports.Exchange Time Is the time when the data is received. (aka receipt time)Interval Start Time A setting used in charts to allow for Future dates,so that weather forecast data may be plotted forward in time.

Example: Weather Data with Respect to Exchange Time and Price Data

The following is an example of charting weather data with respect toexchange time and price data. FIG. 4A is screenshot including a chart ofexample weather forecast data and price data as a function of exchangetime. The example shown in FIG. 4A illustrates a scenario where eachweather Forecast Valid Day is being produced by the weather forecastmodel (source). The x axis describes the “exchange time” which each dot(elements 402, 404) is received. Each dot 402 is a ‘preliminary view’ ofthat day's forecast element (such as daily average temperature, GWDD,HDD, CDD, etc.), in which a condition code (“% complete”) may beginproviding ‘preliminary views’ when a forecast day is 50% (for example)and may stop when that forecast day is completed at 100%. Dot 404 at theend of a forecast valid day is the 100% conclusion.

Not shown here, is the price of any traded commodity using a minuteOpen/High/Low/Close (OHLC) bar. In general, OHLC represents an examplemanner in which traded prices may be displayed, over some time interval(e.g., one minute, five minutes, fifteen minutes, one day, etc.). Forexample, trading data may be organized into one minute intervals and asingle bar may depict the OHLC over each of the one minute time spans(or any suitable time period). In some examples, one minute OHLC barsmay be displayed together with weather “tick” data to aid in identifyingtrading opportunities. The presentation of the combination of the twodata sets on interactive GUI 120 provides advantages, including in makesit easy to visualize and track (including in real-time) when weathermoves in a significant manner to move the price of a traded financialinstrument.

FIGS. 4B-4D are screenshots of an example 16 day weather forecast for aparticular location as a function of exchange time with respect tonatural gas price data. In particular, FIGS. 4B and 4C show an example16 day weather forecast from the 12z GFS weather forecast model in‘exchange time’ for the GWDD variable as it relates to the price ofNatural gas at Henry Hub. FIG. 4D is a screenshot of an example weatheralpha workflow chart as a function of exchange time. As shown in FIG.4D, when GWDD goes down, price should go down and vice-a-versa.

Example of a Guidance Chart

In some examples, the weather symbology of the present disclosure may beused for guidance weather perspective workflows, and may be configuredto generate guidance charts of weather forecast datasets. FIG. 5 is ascreenshot including an example guidance chart associated with aguidance weather workflow, the guidance chart illustrating weatherforecast data as a function of a forward time period. The example chartstarts ‘now’ at the current hour and extends forward in time 16 days(hour-by hour or 0-384 hours into the future) as seen on the x axis andTemperature displayed (in F) on the y axis for Chicago O'Hare airport.Set of curves 502 shows the 0z GEFS Ensemble mean (curve 502-1) as wellas the +1 STD (curve 502-2) and −1STD (curve 502-2) around the mean(curve 502-1). Set of curves 504 shows the 0z ECE Ensemble mean (curve504-1) as well as the +1 STD (curve 504-2) and −1STD (curve 504-2)around the mean (curve 504-1).

Table 4 is an example output of the data behind the same guidance chartwith the weather symbology. In some examples, system 102 may provideusers with the ability to plot this data in various presentation formats(e.g., a data grid, a spreadsheet, a watchlist) and may update theresulting data in real-time as the underlying data input(s) change.

TABLE 4 Example Weather Chart Output Data 0Z +1 STD 0z −1 STD −1 STD +1STD Date Time GEFS 0z GEFS ECE 0z GEFS 0z ECE 0z ECE Feb. 21, 2020 22:0024.4 37 38.3 11.9 28.1 48.5 Feb. 21, 2020 21:00 24.3 36.8 38.9 11.9 28.749 Feb. 21, 2020 20:00 24.2 36.6 39.4 11.8 29.2 49.6 Feb. 21, 2020 19:0024.1 36.5 40 11.8 29.7 50.2 Feb. 21, 2020 18:00 24 36.3 40.5 11.8 30.150.9 Feb. 21, 2020 17:00 23 35.4 38.1 10.6 28.1 48.2 Feb. 21, 2020 16:0022 34.4 35.7 9.5 25.8 45.6 Feb. 21, 2020 15:00 20.9 33.5 33.4 8.3 23.543.2 Feb. 21, 2020 14:00 19.9 32.6 31 7.1 21.1 40.8 Feb. 21, 2020 13:0018.8 31.8 28.6 5.9 18.6 38.6 Feb. 21, 2020 12:00 17.8 31 26.2 4.7 15.936.5 Feb. 21, 2020 11:00 17.9 30.8 26.5 5 16.4 36.5 Feb. 21, 2020 10:0018 30.7 26.7 5.4 16.9 36.5 Feb. 21, 2020  9:00 18.2 30.6 26.9 5.7 17.336.6 Feb. 21, 2020  8:00 18.3 30.6 27.2 6 17.7 36.7 Feb. 21, 2020  7:0018.4 30.6 27.4 6.2 17.9 36.9 Feb. 21, 2020  6:00 18.5 30.6 27.6 6.5 18.237.1 Feb. 21, 2020  5:00 18.7 30.5 28.5 6.9 19.1 37.8 Feb. 21, 2020 4:00 18.9 30.5 29.3 7.3 20 38.6 Feb. 21, 2020  3:00 19.1 30.6 30.1 7.720.8 39.4 Feb. 21, 2020  2:00 19.3 30.6 30.9 8.1 21.5 40.3 Feb. 21, 2020 1:00 19.6 30.7 31.7 8.4 22.1 41.3 Feb. 21, 2020  0:00 19.8 30.9 32.58.7 22.7 42.4 Feb. 20, 2020 23:00 20.1 31 33.1 9.3 23.3 42.9 Feb. 20,2020 22:00 20.5 31.1 33.7 9.8 23.8 43.6 Feb. 20, 2020 21:00 20.8 31.334.3 10.4 24.3 44.2 Feb. 20, 2020 20:00 21.2 31.5 34.8 10.8 24.8 44.9Feb. 20, 2020 19:00 21.5 31.8 35.4 11.2 25.2 45.7

Example: Progression Charts

In some examples, the weather symbology of the present disclosure may beused for progression weather perspective workflows, and may beconfigured to generate progression charts of weather forecast datasets.FIGS. 6A-6C show the convergence of weather forecast models, as theforecast changes over time, from day-to-day for a specific ForecastValid Day, using Progression charts of the present disclosure. Inparticular, FIG. 6A is a screenshot including an example progressionchart associated with a progression weather workflow; FIG. 6B is ascreenshot of an example progression chart illustrating natural gasstorage estimates and weather model progression as a function offorecast date; and FIG. 6C is an example progression chart for severalweather models as a function of forecast date.

In FIG. 6A, as shown in the far left (16 days ago), there was more riskfor today's forecast (Friday February 7^(th)), which appeared to flattenout approximately 5 days prior to today February 7^(th) (yet the modelsstill show a few degrees difference). FIG. 6B, illustrates examplenatural gas storage estimates (reads in the opposite direction of FIG.6A, from right to left).

Example: Accuracy Charts

In some examples, the weather symbology of the present disclosure may beused for accuracy weather perspective workflows, and may be configuredto generate accuracy charts of weather forecast datasets. FIG. 7A is anexample initiation screen for generating an accuracy chart. In someexamples, the weather symbology may easily organize weather forecastmodel data using the FCD and FCH commands, allowing weather forecastaccuracy to be quickly understood via presentation on interactive GUI120. It may be appreciated that any knowledge of which weather forecastis most likely to be correct may be an informational advantage,particularly for interacting with market data.

FIG. 7B is an example accuracy chart associated with an accuracy weatherworkflow. This data display shown in FIG. 7B is an example using theweather symbol structure of the present disclosure using the Accuracystyle codes which begin with FCD.

Example: System Operation

An example of system operation of weather integration server 116 isprovided below. In this example, MR refers to a Model Run, MRD refers toa Model Run Date, MRH refers to a Model Run Hour, MR0 refers to a ModelRun Offset, FDD refers to a Forecast Dated Date, DD refers to a DatedDate, DDO refers to a dated date offset, FCD refers to a ForecastContinuation Day, CDO refers to a Continuation Day Offset, FDH refers toa Forecast Dated Hour, DH refers to a Dated Hour, DHO refers to a DatedHour Offset, FCH refers to a Forecast Continuation Hour, CHO refers to aContinuation Hour Offset., “LOC” refers to location and “REQ” refers torequest. In Table, 5, DM represents a data manager (such as for datacache(s) 124).

Table 5 below illustrates non-limiting examples of system operationaccording to aspects of the present disclosure.

TABLE 5 Examples of System Operation Rolling/ Request Request TypeSpecific DM Underlying Symbol KBOS MR0!-GFS MR Rolling Return KBOSLatest Model Run MRD is REF_DATE: current MR190316_6z-GFS for Bostonfrom calculated 2019 Mar. 16 day's latest Key gets updated GFS from(Today) Forecast every model run. MODEL: GFS Reference data. User may beupdated LOC: KBOS date (Today), Keeps user every model run. REQ: MRNumber of updated of Chart user may clear MRO: 0 Runs in the new modeldown and re-request day and MRO. runs. historical data every NO MRH -Confirmed new model run. use latest clear down Users may receive modelrun for all model data updates (hourly/ hour. run changes. daily) as newdata comes in from data feed. Underlying symbols are updated on modelrun changes. Ex for GFS: 1. KBOS MRYYMMDD_0z-GF 2. KBOS MRYYMMDD_6z-GF3. KBOS MRYYMMDD_12z-GF 4. KBOS MRYYMMDD_18z-GF KBOS MR1!-GFS MR RollingDM may Expired Symbol. Latest Model Run MRD is REF_DATE: return NoUnderlying symbol. (01) for Boston calculated 2019 Mar. 16 expired Usermay be updated from GFS from (Today) symbol. every model run. MODEL: GFSReference MRO: −1 User may Chart user may clear LOC: KBOS date (Today),1 run back get updates down and re request REQ: MR Number of on currenthistorical data every new MRO: −1 Runs in the model runs model run. dayand MRO. for symbol NO MRH - and source. use latest Live Chart model runrequest may hour. generate new historical request for each model runupdate. KBOS MR0!_00z-GFS MR Rolling If current KBOS MR 190316_0z-GFSLatest 00z for MRD is REF_DATE: day has User may be updated Boston fromGFS calculated 2019 Mar. 16 MRH: 0Z every model run and MODEL: GFS from(Today) DM may requested MRH. LOC: KBOS Reference return latest Chartuser may clear REQ: MR day(Today), forecast data down and re-requestMRO: 0 Number of for today historical data every new MRH: 00z Runs inthe with MRH model run. day and MRO. (00z). Else may return expiredsymbol. KBOS MR1!_0Z-GFS MR Rolling DM may Expired Symbol, Last ModelHour MRD can be REF_DATE: return No Underlying symbol 00z calculated2019 Mar. 16 expired User may be updated for Boston from from reference(Today) symbol. every model run and GFS day(Today), User may requestedMRH. MODEL: GFS Number of receive Chart user may clear LOC: KBOS Runs inthe updates on down and re request REQ: MR day, MRO and currenthistorical data every new MRO: −1 MRH. model runs model run. MRH: 00zfor symbol and source. Live Chart request's may generate new historicalrequest for each model run update and MRH. KBOS MR Specific DM may KBOSMR190316_0z-GFS MR190316_0z-GFS MRD is from MRD: return data if Same asclient symbol Return Model run: request Mar. 16, 2019 current day 2019Mar. 16 at (Use format to MRH = 00z is specific Model run: 00z determineday and has data for Boston specific) date for from MRH (00z) MODEL: GFSAnd no LOC: KBOS further REQ: MR updates. MRD: Mar. 16, 2019 if MRD isMRH: 00z current day but MRH is in a future DM may wait until that MRHis received in data feed. KBOS MR MR Specific DM may KBOS MR190316_6z-GFS 190316_6z-GFS MRD is from MRD: return data if Clientsymbol Return Model run: request Mar. 16, 2019 current day 2019 Mar. 16at (Use format to MRH = 06z is specific Model run: 00z determine day andhas data for Boston specific) date for from MRH (00z) MODEL: GFS and noLOC: KBOS further REQ: MR updates. MRD: Mar. 16, 2019 if MRD is MRH: 06zcurrent day but MRH is in future DM may wait until that MRH received indata feed. KBOS FDD8!-GFS FDD Rolling If current KBOS FDD190323-GFS 7 hForecast Dated Forecast REF_DATE: day has the Key gets updated Day fromDated Date is 2019 Mar. 16 interested every day. Today(Currentcalculated (Today) forecast User may be updated day: 1) from date, DMevery model run. MODEL: GFS Reference may return Chart user may clearLOC: KBOS Date and the latest down and re request REQ: FDD DDO forecastdata historical data if DDO: 8 Ex: for that date. needed. Today: Keepsuser 2019 Mar. 16 updated for DDO: 8 days new runs (note current whichhave day: 1) the FDD. Interested Date: 2019 Mar. 23 Database Options:Find all Model Run Dates (or time indexed field)which may haveparticular FDD. Or use an index for Forecast Date to find Data. KBOS FDDSpecific May return KBOS FDD190321-GFS FDD190321-GFS FDD is from FDD:expired Client symbol Data from all request. 2019 Mar. 16 symbol ifModel runs with Database FDD is not forecast for Options: Find currentday. 2019 Mar. 21 all Model Run Subscribes MODEL: GFS Dates (or time andReturns LOC: KBOS indexed field) data if FDD REQ: FDD which may isCurrent FDD: 2019 Mar. 16 have Date and in particular future. FDD. Nofurther Or use an updates after index for FDD goes Forecast Date out ofscope. to find Data. KBOS FDD Rolling If current KBOS FDD12!_00z-GFSForecast REF_DATE: day has the FDD190327_00z-GFS 12^(th) Forecast DatedDated Date is 2019 Mar. 16 interested Key gets updated Day from Todaycalculated (Today) FDD and every day. with Model Run from MRH, DM Usermay be updated Hour of 00z. Reference may return every model run andi.e., 00z runs with Date and the latest requested MRH. forecast date ofDDO. forecast data Chart user may clear 2019 Mar. 27 Ex: for that date.down and re request MODEL: GFS Today: Keeps user historical data if LOC:KBOS 2019 Mar. 16 updated for needed. REQ: FDD DDO: 12 days new runsDDO: 12 Interested which have MRH: 00z Date: the FDD and 2019 Mar. 27MRH. Database Options: Find all Model Run Dates (or time indexed field)which may have particular FDD. Or use an index for Forecast Date to findData. KBOS FCD1!-GFS FCD Rolling Subscribes No Underlying symbol.Forecast Day 1 Use the REF_DATE: and Returns User may be updated (frompossible total Model Run 2019 Mar. 16 data for all every model run. 16(1-17)) Model Limit and (Today) model runs Runs filter with for thatMODEL: GFS FCD. Forecast LOC: KBOS Confirm max Day (1-17). REQ: FCD ‘n’model runs First CDO: 1 limit with Watchlist Model Run Limit: DM. recordMax Model Runs, returned going back to n may be model runs latest updatefor current day. KBOS FCD Rolling Subscribes No Underlying symbolFCD1!_06z-GFS Use the REF_DATE: and Returns User may be updated ForecastDay 1 Model Run 2019 Mar. 16 data for all every model run and (frompossible total Limit and (Today) model runs requested MRH. 16) ModelRuns filter with for that MODEL: GFS FCD and Forecast LOC: KBOS MRH. Day(1-17) REQ: FCD Confirm max with MRH CDO: 1 ‘n’ model runs of 06Z MRH:06z limit with Watchlist Model Run Limit: DM. may be Max Model Runs,empty if going back to n there is no model runs record for FCD and MRH.But DM may update after referenced Forecast Day comes in a Model Run.

Example: Model Run Updates to Users

In some examples, weather integration server 116 may provide one or moremodel run updates in response to latest model run requests and/orrolling back requests from users (e.g., via user device(s) 108).

For a Latest Model Run (MR0) Request, a model run update may be sent forevery new model run for the related source and location. In someexamples, the model run update may be used by the chart user to clear ahistory, such that no new history request may be needed.

For a Rolling Back (MRNN<1-99>) Request, in some examples, when a usersubscribes for a model run going backwards, an expired symbol responsemay be provided (or a different weather response indicating theinformation is historical). From there on forward, the user may beprovided with updates for every new model run for that location andsource.

In some examples, an expired symbol response and model run update may beused by all users (e.g., data may get updates for individual fields) toclear state and chart users re-request historical data from one or moredatabases.

In some examples, when a new model run starts, all chart users may needthe chart to be re-drawn (which may cause weather integration server 116to receive a request for historical data (if not cached) for a previousmodel run). To avoid all chart users requesting historical data at asame time during new model runs, weather integration server 116 mayinclude logic to pre-request data at a pre-defined user interval beforea new run starts.

In some examples, for any rolling request if the user request includes amodel run hour, the user may be notified when that specific model runhour is received from a weather data source(s) data feed.

Example: Forecast Dated Date Requests (FDD) and Forecast ContinuationDay (FCD)

In some examples FDD requests, FDH requests and/or FCD requests may bereceived that may be subscribed to via a previous model run, a currentmodel run and/or for a future model run. FDD and FDH requests relate tothe progression weather perspective, and FCH requests relate to theaccuracy weather perspective (described above).

For example, when a user requests data for FDD and FCD and aresubscribed to current model run, the resulting chart(s) may be updatedfor every new model run for the related source and location. In someexamples, for every new day runs (e.g., 00z), all users with charts openmay have charts re-drawn for FDD/FDH and may request historical data forthat FDD/FDH and FCD/FCH.

For future model runs, a user may subscribe for a future symbol. In thisexample, the user may receive no forecast data response and may receivean update on that symbol when the future event occurs.

In some examples, users may not need to re-request historical data fornew model run updates.

Example: Weather Field Filtering

In some examples, a filter option may be provided in weather impactdashboard 122. The filter option may provide users (e.g., via userdevice(s) 108) the ability to include a filter option to a weatherimpact request. In one example, the format for a filter option may be:

filters=“field_1=<value>&field_2=<value>”

For example, for filtering by daily symbol (interval type=D) and with100% complete, the following filters option may be used:filters=“interval type=D&PercentComplete=100”, where the term “intervaltype” may include Hourly (H, default) and Daily (D). In some examples,if the interval type is not specified, system 102 may lookup intervaltype after inspecting the fields. In some examples, an additionaloptional filter DEBUG=T&columns=* may be used to request all fields.

Example: Model Run Information

In one non-limiting example, weather integration server 116 may providemodel run information for GFS and GEFS weather data models. The modelrun information may include model hours (e.g., 0z, 6z, 12z, 18z, basedon GMT), may provide about 385 hourly records and about 209 dailyrecords.

Example: Symbology Specification

Next, an example symbology specification is described, according to anaspect of the present disclosure.

In this non-limiting example, the symbology for forecasts may include atleast five different methods to retrieve a symbol and/or data. Exampleretrieval methods may include: (i) by symbol type and field, (ii) bysymbol type and aggregation, (iii) by model run and model run date, (iv)by valid day/date-time and (v) by valid day or date. FIG. 8A illustratesan example user interface illustrating examples of symbologyconstruction.

Table 6 illustrates an example symbol list and available fields that maybe used for retrieval by symbol type and field. Table 7 illustrates anexample symbol list and available aggregations that may be used forretrieval by symbol type and aggregation.

TABLE 6 Example Symbol List and Available Fields Symbol Type ExampleIntraday Daily Model Run - Rolling KORD MR0-GFS Yes Yes Model Run -Specific KORD MR190228_12z- Yes Yes GFS Model Run - Rolling run KORDMR0_0z-GFS Yes Yes Horizon Day - Rolling KORD FH13-GFS No Yes HorizonHour - Rolling KORD FHH1-GFS Yes No Horizon Day - Specific KORDFH190228-GFS No Yes Horizon Hour - Specific KORD FH19022812-GFS Yes NoHorizon Day - Rolling run KORD FH12_12z-GFS No Yes Horizon Hour -Rolling run KORD FHH1_18z-GFS Yes No Valid Day - Rolling KORD FD1-GFS NoYes Valid Day - Rolling run KORD FD1_12z-GFS No Yes

TABLE 7 Example Symbol List and Available Aggregations Symbol TypeExample Intraday? Daily? Model Run - Rolling KORD MR0-GFS Yes (hourly)Yes Model Run - Specific KORD MR190228_12z-GFS Yes (hourly) Yes ModelRun - Rolling run KORD MR0_0z-GFS Yes (hourly) Yes Horizon Day - RollingKORD FH13-GFS Yes (4 model run) Yes Horizon Hour - Rolling KORD FHH1-GFSYes (4 model run) Yes Horizon Day - Specific KORD FH190228-GFS Yes (4model run) Yes Horizon Hour - Specific KORD FH19022812-GFS Yes (4 modelrun) Yes Horizon Day - Rolling run KORD FH12_12z-GFS Yes (1 point) YesHorizon Hour - Rolling run KORD FHH1_18z-GFS Yes (1 point) Yes ValidDay - Rolling KORD FD1-GFS Yes (4 model run) Yes Valid Day - Rolling runKORD FD1_12z-GFS Yes (1 point) Yes

The model run and model run date retrieval method represents a ‘vanilla’way of viewing the data. In this example, the time series may becomprised of the different model hours over that model date. The datamay appear similar to a forward curve in the future. The model run andmodel run date retrieval may also include options such as syntheticrolling model run retrieval method and a synthetic rolling model run andmodel time retrieval method. The synthetic rolling model run method mayprogrammatically include the most current model run (versus the previousor previous+1) models. The synthetic rolling model run and model timemethod may programmatically include the most current model run/byselected model time (versus the previous or previous+1) models.

The valid day/date-time retrieval method may allow the user to select apoint in time (e.g., noon on Friday) and analyze how the forecast haschanged on each model run. This retrieval method may be akin to viewinga future going towards expiry, with each model run being a session. Insome examples, this retrieval method may be used for intraday (e.g.,hourly) values.

The valid day or date retrieval method is similar to the date-timeretrieval method, except that the dataset in the valid day/dateretrieval method may include a daily aggregation and a greater number ofsymbols. The valid day/date retrieval method may also include an optionsuch as a synthetic rolling valid day or date retrieval method, whichmay provide the ability to use indices to obtain rolling valid dates.

In some examples, the symbology may be constructed with the followingelements:

Location+Model Name (e.g., GFS)+Model Run

For forecast valid days, the symbology may include:

Location+Model Name+Forecast Continuation <Roll number>

For forecast horizon days (also referred to as Target Date), thesymbology may include:

Location+Model name+Forecast Horizon/Target Date <date/time>

In some examples, the symbology may support one or more types ofconstructions. Table 8 provides an example list of symbol types forvarious constructions. In some examples, it may be desirable that,similar to the continuation symbols, all metadata reflect a prompt-mostdataset in a series. In Table 8, the terms horizontal, diagonal andvertical/column refers to the viewing of the symbology elements withrespect to the columns and rows of the spreadsheet shown in FIG. 8B. Forexample, horizontal refers viewing the symbology with respect to a row,vertical refers to viewing the symbology with respect to a column anddiagonal refers to viewing the symbology with respect to a diagonal line(across a combination of rows and columns).

TABLE 8 Example List of Symbols for Various Constructions Symbol TypeSymbol Notes Model Run - Rolling KORD MR0-GFS Points to core(horizontal) Model Run - Specific KORD MR190228_12z-GFS Core(horizontal) Model Run - Rolling run KORD MR0_0z-GFS Points to core(horizontal) Horizon Day - Rolling KORD FH13-GFS Diagonal Horizon Hour -Rolling KORD FHH1-GFS Diagonal Horizon Day - Specific KORD FH190228-GFSDiagonal Horizon Hour - Specific KORD FH19022812-GFS Diagonal HorizonDay - Rolling run KORD FH12_12z-GFS Diagonal Horizon Hour - Rolling runKORD FHH1_18z-GFS Diagonal Valid Day - Rolling KORD FD1-GFSContinuations of core (vertical/column) Valid Day - Rolling run KORDFD1_12z-GFS Continuations of core (vertical/column)

In some examples, the symbology may include additional condition codes,including one or more of a Daily % Complete code, an Interpolated code,and a Fast/Full code. For example, “fast” and “full” selections may behandled by one or more associated condition codes. In some examples, thesymbology may include additional commodity codes for different %Complete values (e.g., ¼th, ⅛th, 1/24th, etc., depending on the modeland forecast day). In some examples, the “% Complete” value may beprovided at 50% or higher.

In some examples, the symbology may include different selectionpresentation behavior depending on which condition codes are selected.In some examples, a default behavior for presenting any charts mayinclude presenting a highest percent complete available for any point.In some examples, if a “100% complete” code is selected, then no other %complete conditions may be shown. In some examples, a default behaviorfor a “Fast/Full” condition code may include presenting a “latest”(typically full) (e.g., unless the full information hasn't yet arrived).In some examples, if “Full” code is selected, the “Fast” value may notbe shown. In some examples, if the “Interpolated” condition code isselected as the default behavior, interpolated data may be presented. %Complete, for example (e.g., ¼ths, ⅛ths, 1/24ths, depending on the modeland forecast day).

In some examples, the symbology may include condition codes for thefront end (e.g., an interactive GUI, a spreadsheet, etc.), such ascondition codes in “Time and Sales”, and may provide additional fieldsfor a forecast valid hour/day. In some examples, the symbology mayprovide for updates to values in one or more charts. In some examples,the symbology may provide the ability to filter tick charts by “%complete” and/or interpolation by symbol. In some examples, a samesymbol and different % completes may be provided in a same chart. Insome examples, data may be pulled into a spreadsheet via time and/orsales information.

In some examples, the symbology may use metadata including, withoutbeing limited to, one or more of latitude (“Lat”), longitude (“Long”),altitude, elevation, a description, description information fromICAO/WMO/WBAN/USAF/CRN/SNOTEL (if available), station start, station endand time zone. In some examples, the symbology may use one or more ofinterval start information (e.g., start of a hour/day referenced),interval end information (e.g., end of an hour/day referenced) andreceived time information. In some examples, a default selectionbehavior may be provided, such as in a GUI, in flex metadata and thelike. Table 9 provides examples of default interval type by symbol.

TABLE 9 Examples of Default interval type by symbol Symbol Type SymbolStart End Received Model Run - Rolling KORD MR0-GFS Yes Yes Yes ModelRun - Specific KORD MR190228_12z-GFS Yes Yes Yes Model Run - Rolling runKORD MR0_0z-GFS Yes Yes Yes Horizon Day - Rolling KORD FH13-GFS Yes YesYes Horizon Hour - Rolling KORD FHH1-GFS Yes Yes Yes Horizon Day -Specific KORD FH190228-GFS Yes Yes Yes Horizon Hour - Specific KORDFH19022812-GFS Yes Yes Yes Horizon Day - Rolling run KORD FH12_12z-GFSYes Yes Yes Horizon Hour - Rolling run KORD FHH1_18z-GFS Yes Yes YesValid Day - Rolling KORD FD1-GFS Yes Yes Yes Valid Day - Rolling runKORD FD1_12z-GFS Yes Yes Yes

In some examples, system 102 may provide an example display frequency ofat least about 10,000 points a minute (e.g., at irregular intervals),and may include an example latency of less than about 1 second responseto desktop and/or client applications (e.g., clientapplication(s)/service(s) 126). In some examples, weather integrationserver 116 may provide an example non-historical forecast decay, where,after 48 hours from release, non-historical data may decay, and whereall historical data may remain (including, in some examples, remainingindefinitely).

In some examples, weather integration server 116 may include historyrequirements such as no backfill for missing data and examplecorrections (including no corrections options) for data having anyerrors.

In some examples, weather integration server 116, in addition toproviding fields for the presentation of integrated weather data, mayprovide ensemble fields (which may reflect the set of ensemble runs).Non-limiting examples of ensemble fields may include temperature, GWDDDand precipitation. In some examples, weather integration server 116 mayalso provide one or more ensemble field sets including, without beinglimited to, an average, a minimum, a maximum, a standard deviation, 10%,25%, 50%, 75% and/or 90% variables.

In some examples, weather integration server 116 may provideuser-selectable options for watchlist values. In some examples, valuesmay be with respect to a “Latest” received. For example, a watchlistvalue for a model run may refer to a latest point in time, a watchlistvalue for a valid day may refer to a most recently received value, and awatchlist for a horizon day may refer to a most recently received value.In some examples, a same field may be configured to have differentvalues for a same location, depending on the symbology term used. Insome examples, interval start and interval end fields in the watchlistmay update with a latest update. In some examples, the watchlist mayprovide a cleardown style behavior. In some examples, cleardown logicmay not be applied, when a rolling contract points to a new model rundataset which doesn't yet have data (e.g., a blank value may be shown).For example KORD FVD18-GFS.GWDD may be presented as blank while themodel run is now starting to be available, but the value for day 18 isnot completed. The use of cleardown logic in suitable circumstances (andnot using cleardown logic in some circumstances) may be useful forviewing the data in the watchlist.

In some examples, weather integration server 116 may provide varioustypes of data usage (e.g., depending upon the type of clientapplication/service 126). In some examples, data usage for a tradingdesktop may include presentation of about 1 to 20 charts (where eachchart may include about 1 to about 25 time series points), about 1 toabout 10 grids (where each grid may include at least thousands ofindividual requests) and may provide one or more spreadsheets (whereusers may maybe greater than about 5000 datapoint requests and mayprovide greater than about 100 time series refreshes at a time).

Examples of an Interactive GUI

Next, examples of an interactive GUI 900 for providing interactive toolsfor viewing and interacting with integrated weather and market data aredescribed with respect to FIGS. 9A-9H. In some examples, interactive GUI900 may represent an example of weather impact dashboard 122 (FIG. 1 ).

In some examples, interactive GUI 900 may include one or more windows,such as window 902 and window 904. In some examples, window 902 mayinclude user input region 906 (e.g., for providing a weather datarequest that may correspond to a weather symbology instruction). In someexamples, window 902 may further include display region 906 fordisplaying weather and/or market data. In some examples, display region906 may include an interactive display. FIG. 9B shows a portion ofdisplay region 910 of interactive GUI 900 illustrating an example chart.FIG. 9C shows window 912 of interactive GUI 900 illustrating an exampleintegrated weather and market data chart. FIG. 9D shows window 914 ofinteractive GUI 900, illustrating options for bias and bias adjustedoverlays. FIG. 9E shows window portion 916 of interactive GUI 900,illustrating options for creating a customizable marker. FIG. 9F showswindow 918 of interactive GUI 900, illustrating options for creatingcondition alerts. FIG. 9G shows window 920 of interactive GUI 900,illustrating options for managing custom markers. FIG. 9H shows aportion of window 922 of interactive GUI 900, illustrating an examplegrid display. It should be understood that FIGS. 9A-9H represents anon-limiting example user interface, and that a differing interfaceconfigured in accordance with this disclosure may be provided forproviding presentation and interaction with integrated weather andmarket data.

In some examples, interactive GUI 900 may include global controls suchas time zone support and at least one weather properties section forselecting weather properties (e.g., Celsius/Fahrenheit, Mm/in (precip),M/Feet (Waves), Hpa/inhg/mmhg (pressure) and Mph/kmh/mps (wind)). Insome example, interactive GUI 900 may include user-selectable optionsfor chart presentation (e.g., an ability to add intervalstart/end/received to any chart (interval start=Forecast Valid), anability to add % complete, an ability to add various conditions codes(e.g., % complete, fast/full, interpolated, not interpolated), and anability to add various interval time values (e.g., received, start,end)).

In some examples, interactive GUI 900 may include user-selectableoptions for weather objects. For example, users may be able to applyvarious criteria to their charts through the boxes shown in user inputregion 906 of window 902 (FIG. 9A). In some examples, criteria boxes canbe hidden/displayed when clicking the screener button in the upper rightcorner (in window 902). In some examples, if the user has entitlementsfor weather, and a weather symbol is entered into the top left, in someexample a button will appear.

In some examples, configurable objects in a weather window may includelocation region control (this is a type-ahead search only on weathersymbols), model run (e.g., 0z, 6z, 12z, 18z, current model run,current+6 hrs ago, current+12 hrs ago, current+18 hrs ago, current+24hrs ago), model (e.g., GFS, GEFS, etc.), symbol granularity (daily,synthetic hourly, raw data), climatology overlay (e.g., NWS 30 yr, Trail30 yr, Trail 15 yr, Highest, 1+std, Mean, −1 std, Lowest), and studies(e.g., accumulate, show with bias, show only bias, summary stats only).

In some examples, interactive GUI 900 may provide an ability to save acriteria and view modify existing weather window views. In someexamples, interactive GUI 900 may be configured to provide a display ofdata based on criteria that can be filtered through user entry,selection, suggested values, other, to filter results based on users'needs. Example controls available may include checkboxes, radio buttons,ranges and/or manually entered alpha/numerical values. In some examples,users may be permitted to temporarily turn on/off criteria by clickingon, for example, a green light at upper left of criteria box for what ifscenarios. In some examples, criteria boxes may be collapsed to offermore screen real estate for a data view. This operation may beperformed, for example, by clicking a double arrow on the bottom left oftoolbar. Criteria filtered entries may still visible in collapsed mode.In some examples, users may be permitted to still modify criteriafilters in collapsed mode by clicking on highlighted text. In someexamples, users may save criteria sets for easy recall of filtered sets.

In some examples, interactive GUI 900 may provide options for studyingthe impact of weather data on market data. For example, interactive GUI900 may provide climatology overlays. In some examples, statisticalranges for the overlays may take a portion of or all weather series in achart as input. Examples of the statistical ranges may include a highesthigh, an upper 1 sigma, a lower 1 sigma, a lowest low and a mean. Insome examples, interactive GUI 900 may also provide options for bias andbias adjusted overlays (see, FIG. 9D).

In some examples, interactive GUI 900 may provide user-selectableoptions for markers enhancement. In some examples, the markersenhancement options may include the ability to create a new customizablemarker (e.g., when a user clicks “Customize” from the Markers drop down,they may see a window similar to custom alerts). (See FIGS. 9E and 9F.)In some example, the markets enhancement options may include a way totoggle between all events where the expression is true, and when thefirst event occurs (cross over). For example, If KORD DIFF-GFS >4 ANDKORD Change-GFS >4. In some examples, markers may use an interval startfor cross reference. In some examples, markers may contain metadata onhover (e.g., value, expression, time received). In some examples, awindow may be provided for managing custom markers (see FIG. 9G).

In some examples, interactive GUI 900 may be configured to provide auser with options to generate a watchlist. One example use case is usingthe FV day type symbols to pull in GWDD as the data arrives. In someexamples, interactive GUI 900 may include additional weathercolorization logic for the watchlists.

In some examples, interactive GUI 900 may be configured to generate oneor more grids. In some examples, a grid may be the primary location forcreating displays of this weather data. In some examples, the grid mayinclude an ability to pull out history for any hourly point, dailypoint, and any historical field. In some examples, additional gridsyntax may be provided to filter on new weather condition codes (e.g.,interpolated, % complete, fast vs. full). In some examples, additionalgrid syntax may be provided to request data by different timelineindices (e.g., start, end, received). In some examples, additional gridcoloration logic may be provided for weather (e.g., which may be userdefined in weather global parameters). See FIG. 9H for an example of agrid.

Referring next to FIGS. 10A-10K, examples of an interactive GUI 1000 forproviding interactive tools for viewing and interacting with integratedweather and market data are described, according to another aspect ofthe present disclosure. In some examples, interactive GUI 1000 mayrepresent an example of weather impact dashboard 122 (FIG. 1 ). Itshould be understood that FIGS. 10A-10K represent a non-limiting exampleuser interface, and that a differing interface configured in accordancewith this disclosure may be provided for providing presentation andinteraction with integrated weather and market data.

In some examples, interactive GUI 1000 may include weather landing page1002, as shown in FIG. 10A. Weather landing page 1002 may includevarious regions 1004-1014 (shown in detail in respective FIGS. 10B-10F)for viewing and interacting with user-customizable weather and marketdata in real-time (including weather data integrated with market data),and for creating user-customizable watchlists and alerts. In someexamples, weather landing page 1002 may include weather alpha region1004 (shown in FIG. 10B), map region 1006 (shown in FIG. 10C), modelstatus region 1008 (shown in FIG. 10D), watchlist region 1010 (shown inFIG. 10F), drill around region 1012 (shown in FIG. 10F) and alertsregion 1014 (shown in FIG. 10E). Weather landing page 1002 may alsoinclude one or more additional selectable tabs (e.g., hourlymeteorology, hourly guidance, etc.) as shown in FIG. 10A) which may openone or more additional windows, pop-up windows and/or regions in weatherlanding page 1002.

Referring to FIG. 10B, in some examples, weather alpha region 1004 maybe configured to present live streaming weather-alpha data for displayand user-interaction, including integrated live streaming weather dataand live streaming market price data. Weather alpha region 1004 may alsobe configured be configured to receive user input (e.g., via one or moreuser buttons, drop down menus, text boxes and the like). In someexamples, hovering over a location by a pointing device (e.g., a mouse)may cause weather alpha region 1004 to present additional information.In some examples, weather alpha region 1004 may be configured to presentlive streaming weather and price in accordance with a specific location(e.g., a specific trading location) in an graphical format. In someexamples, the weather data may be expressed in one or more “trader” timeperiods (e.g., NG weeks, Calendar weeks, etc.) to better match any timeperiods for transacting in any desired financial instruments.

In general, weather alpha region 1004 may be configured to depict howweather forecasts (e.g., changing weather perceptions and/or anomalisticweather) may move commodity prices, in real-time. Weather alpha region1004, may be used, together with the weather symbology of the presentdisclosure to create unique (and user-customizable) financial weatherworkflows and provide unique transformational integrated weather andprice visualizations. Such unique and customizable integrated weatherand price visualizations are exclusive to the present disclosure and donot exist in conventional systems. Although it is generally known thatweather versus price relationships may exist, challenges exist inquantifying market efficiencies/inefficiencies of market price digestingthis information, as well as any frequency of occurrences, a marketbreadth of weather impacts and a magnitude of the price changes relatedto changing weather perceptions. Interactive GUI 1000 (including weatheralpha region 1004), through the unique integrated and customizedpresentation of live weather and market data, significantly improvesthis type of weather/price analysis and provides such data andinformation in an easily accessible manner for various types of users(e.g., in the financial community), and brings a once analog weathermarket into a streamlined digital workflow.

In some examples, weather alpha region 1004 may include options forproviding weather alpha information according to an alpha micropresentation or an alpha macro presentation. For an alpha micropresentation, weather alpha region 1004 may provide the fastest and mostdetailed views of changing weather perspectives (e.g. from keygovernment entity forecasts) overlaid with real-time market prices. Insome examples, an alpha micro presentation may use preliminary dailyvalues processed in real-time from hourly forecast data, to deliver anearly view of forecasted daily temps & GWDD, minutes in advance ofalternate weather providers. For an alpha macro presentation, weatheralpha region 1004 may provide a comprehensive qualitative review over anentire trading day (or multiple trading days) showing how variousweather forecast models (including various model runs) have influencedmarket prices (for any instrument). In some examples, the alpha macropresentation may provide a quick qualitative view of a directionalrelationship between weather and price data.

Referring to FIG. 10C, map region 1006 may be configured to present oneor more weather maps, including live streaming weather maps. In someexamples, the weather map(s) may presented in a graphical format and mayinclude various colorizations (e.g., to indicate weather informationsuch as temperature gradations). In some examples, map region 1006 mayprovide user input options for selecting and customizing various typesof weather maps. The presented weather maps in map region 1006, workingin concert with the presented weather and price information in weatheralpha region 1004, may allow the user to view big picture impacts ofweather, for example, the impacts of weather about to enter into aregion of interest of a weather map. In some examples, map region 1006may deliver weather nap(s) within seconds after government entityweather forecasts are made available into the public domain. In someexamples, the weather maps may include maps related to one or more ofhourly weather data, daily weather data, multi-day weather data,seasonal/performance data, weather anomaly data and change of weather.The weather maps may include one or more comprehensive maps covering theEarth's sub-surface, surface, upper air, along with liquid/frozenprecipitation, renewables, etc.

In some examples, weather map(s) presented in map region 1006 may dependon a particular weather workflow. In a guidance workflow, weather map(s)may be presented in such a manner to easily compare a number of weatherforecasts for relative agreement/disagreement (e.g., a forecast risk).In a progression workflow, weather map(s) may be presented in such amanner to hold target data constant to view how all weather forecastshave changed over time for a specific target date. In a performanceworkflow, weather map(s) may be presented in a manner to help understandweather forecast accuracy (e.g., by exploring warmer/coder bias or meanabsolute error).

In some examples, seasonal map(s) may be configured in a manner toeasily compare and contrast longer range weather forecasts (e.g.,covering a balance-of-the-month, a prompt month, a next two seasons,etc.). In some examples, map region 1006 may include user options forselecting various streaming weather maps (e.g., geographic region, timeperiod (e.g., hourly, daily, multi-day), model run date, weather maptype and/or popular maps). In some examples, options for a geographicregion may include options for global, regional, tropics and GIS.

Referring to FIG. 10D, in some examples, model status region 1008 mayprovide real-time (e.g., up-to-date) status information of variousweather model downloads. In some examples, model status region 1008 mayinclude user-customizable options for presentation of model statusinformation. In some examples, model hours may be organized intoForecast Valid Days (rows) based upon a selected time zone, and maydisplay percentage (%) complete for the particular model. In general,the model status information presented in model status region 1008 mayprovide a snapshot of the weather models, to indicate when the weatherforecast models have loaded and whether there are any delays and/ormissing data. In some examples, the status information may be displayedin various colorizations. For example, for weather models/model runs, agreen line may indicate the model is “currently running”. A green statusvalue may indicate that a specific model hour has arrived “on-time” asexpected (e.g., based upon timestamps from the trailing fourteen days).A yellow status value may indicate that a specific model hour arrivedslower than a trailing (for example) 14 day average (e.g., outside 1standard deviation). A red status value may indicate that the specificmodel hour should have arrived (e.g. at least five minutes ago) and isstill missing.

Referring to FIG. 10F, in some examples, watchlist region 1010 mayprovide one or more user-input options for creating a user-customizablewatchlist of one or more selectable financial instruments that may belinked to a desired (e.g., optimal) weather location. In some examples,drill around region 1012 may include one or more drill-Around boxesassociated with one or more financial instruments. The drill-aroundbox(es) may provide one or more options related to one or more desiredweather symbologies associated with the particular financialinstrument(s).

Referring to FIG. 10E, in some examples, alerts region 1014 may includeuser-input options for creating customizable weather alerts, such aschanging weather forecast(s) that may be considered by the particularuser to be “significant.” In some examples, alerts region 1014 maypresent active weather alerts, options to allow a user to add newweather alerts and/or options to view a history of one or more(including all) weather alerts which have been triggered. Theinformation provided in alerts region 1014 may allow users to moreconfidently cover more weather influenced instruments with greaterprecision and confidence. In some examples, an alert may direct a userto specifically designed workbook when the alert is triggered.

Although exemplary regions are depicted in FIG. 10A, alternateconfigurations for the regions are envisioned. For example, a graphicaluser interface may contain more or fewer regions. Additionally, theregions may be reorganized in any manner and display other pertinentinformation.

FIG. 10G illustrates an example weather alert set up window 1016 (window1016 herein) of interactive GUI 1000. Window 1016 represents a wizardfor creating user-customizable weather alerts. In general, customizableweather alerts may allow a user to monitor streaming weather forecasts,and identify (user-specified) changes expected (by the user) to have amarket impact. Window 1016 may include one or more user input regionsfor adding a new (user-customizable) weather alert (which may bepresented in alerts region 1014 (FIG. 10E). In a non-limiting example,window 1016 may include location input region 1018, alert thresholdinput region 1020, weather model selection region 1022 and notificationselection region 1024.

Location input region 1018 may provide a user input region for userinput of one or more desired weather location. Alert threshold inputregion 1020 may include options for user input of one or morethresholds, to create one or more conditions for triggering an alert. Insome examples, alert threshold input region 1020 may include options forscanning through historical data to select appropriate alert thresholdsand/or a notes region for user input for indicating special notes (e.g.,bullish/bearish) linked to an financial instrument. In some examples,weather model selection region 1022 may include user input options forselecting one or more models, one or more model runs, one or moreforecast periods, forecast valid days to scan and at least onepercentage complete value to utilize for the forecast. In some examples,notification selection region 1024 may include user input options forselecting one or more days a user desires the alert(s) to be active.

FIG. 10H illustrates an example weather perspective selection window1026 of interactive GUI 1000 when workflow selector region 1028 isselected for a guidance workflow (also referred to herein as guidancewindow 1026). In general, weather perspective selection window 1026represents a weather wizard for creating user-customizable charts forvarious weather perspectives (e.g., weather workflow(s), weatheralpha(s)). The Guidance workflow may be configured to present weatherdata in a manner to help the user to understand forecast risk (e.g.,relative agreement & disagreement among forecasts). The guidanceworkflow may provide another unique perspective to view same day weatherforecasts, and how current weather forecasts relate to previous years.

Guidance window 1026 may include one or more user input regions forcreating a user-customized guidance workflow. In a non-limiting example,guidance window 1026 may include location input region 1030 forselecting one or more weather locations, time interval input region 1032for selecting hourly or daily time intervals, weather model selectionregion 1034 and observations selection region 1036. In some examples,weather model selection region 1034 may include user input for selectingone or more weather forecast models, one or more model runs, anyensemble statistics and one or more climatology options. Observationsselection region 1036 may include user input options for observing thedata, including real-time observations and historical weather forecasts.

In some examples, workflow selector region 1028 may include a weatherworkflow option for seasonal analysis (not shown). The seasonal analysisworkflow may be configured to present data to easily compare years whoseweather pattern(s) maybe similar to a current season, along with variousclimatologies. In some examples, the seasonal analysis workflow may beconfigured to overlay long range weather forecasts to gain a uniquefuture perspective, which forecasts may be monitored in real-time as theforecast models are updated.

FIG. 10I illustrates an example weather perspective selection window1038 of interactive GUI 1000 when workflow selector region 1028 isselected for an accumulation workflow (referred to herein asaccumulation window 1038). In general, accumulation window 1038 mayinclude user input regions similar to guidance window 1026, but withdifferent options associated with creating an accumulation workflow. Ingeneral, the accumulation workflow may be configured to present data toprovide a seasonal perspective to accumulated snow, precipitation,degree days, etc., to help analyze general market trends (e.g., seasonsbeing above/below average).

FIG. 10J illustrates an example weather perspective selection window1040 of interactive GUI 1000 when workflow selector region 1028 isselected for a progression workflow (referred to herein as progressionwindow 1040). In general, progression window 1040 may include user inputregions similar to guidance window 1026, but with different optionsassociated with creating a progression workflow. In general, aprogression workflow may be configured to present data to help usersunderstand “convergence” of weather forecasts (e.g. when forecasts beginto agree with each other) as well as run-to-run volatility and meanreversion information.

FIG. 10K illustrates an example weather perspective selection window1042 of interactive GUI 1000 when workflow selector region 1028 isselected for an alpha micro workflow (referred to herein as alpha microwindow 1040). In general, alpha micro window 1042 may include user inputregions similar to guidance window 1026, but with different optionsassociated with creating an alpha micro workflow. In some examples,workflow selector region 1028 may also include an alpha macro window forcreating a user-customized alpha macro workflow (not shown). In someexamples, the alpha macro workflow may provide a quick qualitative viewof the directional relationship between weather and price data overmultiple model runs and/or multiple days. In general, a weather alphaworkflow (e.g., alpha macro, alpha micro) may be configured to presentforecasted GWDD from each weather forecast model, as it is released inthe public domain vs price data. In some examples, the weather alphaworkflow may be configured for such that a user may quickly scan acrossmany different weather models and model runs and identify if the weathermay be driving market price(s).

Computer Architecture

Systems and methods of the present disclosure may include and/or may beimplemented by one or more specialized computers including specializedhardware and/or software components. For purposes of this disclosure, aspecialized computer may be a programmable machine capable of performingarithmetic and/or logical operations and specially programmed to performthe functions described herein. In some embodiments, computers maycomprise processors, memories, data storage devices, and/or othercommonly known or novel components. These components may be connectedphysically or through network or wireless links. Computers may alsocomprise software which may direct the operations of the aforementionedcomponents. Computers may be referred to as servers, personal computers(PCs), mobile devices, and other terms for computing/communicationdevices. For purposes of this disclosure, those terms used herein areinterchangeable, and any special purpose computer particularlyconfigured for performing the described functions may be used.

Computers may be linked to one another via one or more networks. Anetwork may be any plurality of completely or partially interconnectedcomputers wherein some or all of the computers are able to communicatewith one another. It will be understood by those of ordinary skill thatconnections between computers may be wired in some cases (e.g., viawired TCP connection or other wired connection) or may be wireless(e.g., via a WiFi network connection). Any connection through which atleast two computers may exchange data can be the basis of a network.Furthermore, separate networks may be able to be interconnected suchthat one or more computers within one network may communicate with oneor more computers in another network. In such a case, the plurality ofseparate networks may optionally be considered to be a single network.

The term “computer” shall refer to any electronic device or devices,including those having capabilities to be utilized in connection with anelectronic information/transaction system, such as any device capable ofreceiving, transmitting, processing and/or using data and information.The computer may comprise a server, a processor, a microprocessor, apersonal computer, such as a laptop, palm PC, desktop or workstation, anetwork server, a mainframe, an electronic wired or wireless device,such as for example, a telephone, a cellular telephone, a personaldigital assistant, a smartphone, an interactive television, such as forexample, a television adapted to be connected to the Internet or anelectronic device adapted for use with a television, an electronic pageror any other computing and/or communication device.

The term “network” shall refer to any type of network or networks,including those capable of being utilized in connection with the systemsand methods described herein, such as, for example, any public and/orprivate networks, including, for instance, the Internet, an intranet, oran extranet, any wired or wireless networks or combinations thereof.

The term “computer-readable storage medium” should be taken to include asingle medium or multiple media that store one or more sets ofinstructions. The term “computer-readable storage medium” shall also betaken to include any medium that is capable of storing or encoding a setof instructions for execution by the machine and that causes the machineto perform any one or more of the methodologies of the presentdisclosure.

FIG. 11 illustrates a functional block diagram of a machine in theexample form of computer system 1100 within which a set of instructionsfor causing the machine to perform any one or more of the methodologies,processes or functions discussed herein may be executed. In someexamples, the machine may be connected (e.g., networked) to othermachines as described above. The machine may operate in the capacity ofa server or a client machine in a client-server network environment, oras a peer machine in a peer-to-peer (or distributed) networkenvironment. The machine may be any special-purpose machine capable ofexecuting a set of instructions (sequential or otherwise) that specifyactions to be taken by that machine for performing the functionsdescribe herein. Further, while only a single machine is illustrated,the term “machine” shall also be taken to include any collection ofmachines that individually or jointly execute a set (or multiple sets)of instructions to perform any one or more of the methodologiesdiscussed herein. In some examples, one or more of components 112-128 ofDID system 102, weather data source(s) 104, market data source(s) 106and/or user device(s) 108 may be implemented by a specialized machine,particularly programmed to perform certain functions, such as theexample machine shown in FIG. 11 (or a combination of two or more ofsuch machines).

Example computer system 1100 may include processing device 1102, memory1106, data storage device 1110 and communication interface 1112, whichmay communicate with each other via data and control bus 1118. In someexamples, computer system 1100 may also include display device 1114and/or user interface 1116.

Processing device 1102 may include, without being limited to, amicroprocessor, a central processing unit, an application-specificintegrated circuit (ASIC), a field programmable gate array (FPGA), adigital signal processor (DSP) and/or a network processor. Processingdevice 1102 may be configured to execute processing logic 1104 forperforming the operations described herein. Processing device 1102 mayinclude a special-purpose processing device specially programmed withprocessing logic 1104 to perform the operations described herein.

Memory 1106 may include, for example, without being limited to, at leastone of a read-only memory (ROM), a random access memory (RAM), a flashmemory, a dynamic RAM (DRAM) and a static RAM (SRAM), storingcomputer-readable instructions 1108 executable by processing device1102. Memory 1106 may include a non-transitory computer readable storagemedium storing computer-readable instructions 1108 executable byprocessing device 1102 for performing the operations described herein.For example, computer-readable instructions 1108 may include operationsperformed by components 112-128 of DID system 102, including operationsshown in FIGS. 3A and 3B. Although one memory device 1106 is illustratedin FIG. 11 , in some examples, computer system 1100 may include two ormore memory devices (e.g., dynamic memory and static memory).

Computer system 1100 may include communication interface device 1112,for direct communication with other computers (including wired and/orwireless communication) and/or for communication with a network. In someexamples, computer system 1100 may include display device 1114 (e.g., aliquid crystal display (LCD), a touch sensitive display, etc.). In someexamples, computer system 1100 may include user interface 1116 (e.g., analphanumeric input device, a cursor control device, etc.).

In some examples, computer system 1100 may include data storage device1110 storing instructions (e.g., software) for performing any one ormore of the functions described herein. Data storage device 1110 mayinclude a non-transitory computer-readable storage medium, including,without being limited to, solid-state memories, optical media andmagnetic media.

While the present disclosure has been discussed in terms of certainembodiments, it should be appreciated that the present disclosure is notso limited. The embodiments are explained herein by way of example, andthere are numerous modifications, variations and other embodiments thatmay be employed that would still be within the scope of the presentdisclosure.

The invention claimed is:
 1. A method, the method comprising: providinga data distribution system in communication with one or more weatherdata source systems, one or more market data source systems and at leastone user device via at least one network, the data distribution systemcomprising a processing device and a memory storing computer-readableinstructions; collecting, by the data distribution system, weather datafrom among the one or more weather data source systems; generating, bythe data distribution system, at least one weather forecast dataset fromamong the collected weather data; collecting, by the data distributionsystem, financial market data from among the one or more market datasource systems; integrating, by the data distribution system, theweather forecast dataset and a portion of the collected financial marketdata; generating, by the data distribution system, an interactivegraphical user interface (GUI) for display on the at least one userdevice; displaying, via the interactive GUI, a presentation package thatincludes the weather forecast data set integrated with said portion ofthe collected financial market data; and updating the presentationpackage on the interactive GUI concurrent with changes to one or more ofthe weather data, the financial market data and user input received viathe at least one user device, wherein the presentation package furtherincludes an interactive presentation of one or more of at least oneweather forecast map, at least one weather alpha region indicating acombination of weather forecast data and the collected financial marketdata, at least one weather perspective chart associated with apredetermined weather perspective workflow, at least one model statusregion, at least one watchlist region, at least one alerts region, atleast one chart, at least one table, at least one weather grid, at leastone analytic value and at least one user input window for customizingthe interactive presentation.
 2. The method of claim 1, the methodfurther comprising: storing, in at least one database accessible by thedata distribution system, a weather symbology comprising one or moresymbol elements linked to segments of the collected weather data and oneor more pre-defined rules for generating weather symbology instructionshaving a pre-defined instruction structure.
 3. The method of claim 2,the method further comprising: receiving, via the interactive GUI, inputcomprising a weather data request from the at least one user device, anddetermining, by the data distribution system, a weather symbologyinstruction based on at least one requested symbol element indicated inthe received weather data request and in accordance with the one or morepre-defined rules.
 4. The method of claim 3, wherein the generating ofthe at least one weather forecast dataset is based, at least in part, onthe weather symbology instruction.
 5. The method of claim 3, wherein theweather symbology instruction is included in the weather data request orthe weather data request is converted to the weather symbologyinstruction.
 6. The method of claim 3, the method further comprising:extracting, by the data distribution system, at least one segment amongthe segments of the collected weather data corresponding to the at leastone requested symbol element in the weather symbology instruction. 7.The method of claim 3, wherein the weather forecast dataset includes atleast one weather forecast stitched together from among the collectedweather data in accordance with the weather symbology instruction. 8.The method of claim 2, wherein the one or more symbol elements areassociated with one or more of at least one weather forecast model, atleast one weather observation location and at least one predeterminedweather workflow structure.
 9. The method of claim 8, wherein the atleast one predetermined weather workflow structure includes one or moreof at least one weather alpha, a guidance perspective, a progressionperspective and an accuracy perspective.
 10. The method of claim 8,wherein the interactive GUI includes at least one wizard window foruser-customization of the at least one predetermined weather workflowstructure.
 11. The method of claim 2, wherein the weather symbologyfurther includes one or more weather variables comprising at least oneof predetermined fields and predetermined conditions, the weathersymbology instruction further determined based on at least one requestedweather variable among the one or more weather variables received in theweather data request.
 12. The method of claim 1, wherein the collectedweather data includes weather observation data and weather forecastmodel data.
 13. The method of claim 12, wherein the weather observationdata includes at least one of Meteorological Aerodrome Report (METAR)data and Climate Forecast System Reanalysis (CFS-R) data.
 14. The methodof claim 12, wherein the weather forecast model data is associated withat least one of a Global Forecast System (GFS), a GFS ensemble (GFSENS), a GFS ensemble Extension (GFS ENS EXT), a Climate Forecast System(CFS) ensemble, a European Center for Medium-Range Weather Forecast(ECMWF), a ECMWF ensemble (ECMWF ENS), a ECMWF ensemble Extension(EXCMWF ENS EXT), a ECMWF Seasonal (SEAS) and a ECMWF Seasonal Extension(SEAS EXT).
 15. The method of claim 1, wherein the collected weatherdata and the collected financial market data includes at least one ofstreaming data and static data.
 16. The method of claim 1, the methodfurther comprising: displaying, via the interactive GUI, at least oneweather map generated from among the collected weather data.
 17. Themethod of claim 1, wherein the generating of the weather forecastdataset further comprises generating the weather forecast dataset as afunction of an exchange time associated with the collected financialmarket data.
 18. The method of claim 1, the method further comprising:exposing, by the data distribution system, the presentation package toat least one application programming interface (API).
 19. The method ofclaim 1, wherein the interactive GUI is configured to operate on atleast one of a trading desktop, a mobile application and a spreadsheetapplication.
 20. The method of claim 1, wherein the weather datacomprises one or more data streams received via at least one data feed,and wherein the financial market data comprises one or more financialmarket data streams received via the at least one data feed, the methodfurther comprising: segmenting, by the data distribution system, thereceived one or more weather data streams based on one or morepre-defined symbol elements to form at least one segmented weather datastream; extracting by the data distribution system, one or more segmentsof the at least one segmented weather data stream to form at least oneextracted weather stream; generating, by the data distribution system, areal-time weather dataset from the at least one extracted weatherstream; integrating, by the data distribution system, the real-timeweather forecast dataset with the received one or more financial marketdata streams to form part of an integrated presentation package; atleast one of: exposing, by the data distribution system, the integratedpresentation package to at least one application programming interface(API) and displaying the integrated presentation package via theinteractive GUI on a display of the at least one user device; andupdating the integrated presentation package concurrent with changes toone or more of the one or more weather data streams and the one or morefinancial market data streams, wherein the integrated presentationpackage further includes an interactive presentation of one or more ofat least one weather forecast map, at least one weather alpha regionindicating a combination of weather forecast data and financial marketdata, at least one weather perspective chart associated with apredetermined weather perspective workflow, at least one model statusregion, at least one watchlist region, at least one alerts region, atleast one chart, at least one table, at least one weather grid, at leastone analytic value and at least one user input window for customizingthe interactive presentation.
 21. The method of claim 20, the methodfurther comprising: creating, by the data distribution system, thereal-time weather dataset in accordance with a weather symbologyinstruction.
 22. The method of claim 21, wherein the weather symbologyfurther includes one or more weather variables comprising at least oneof predetermined fields and predetermined conditions, the weathersymbology instruction being created in accordance with at least oneweather variable among the one or more weather variables.
 23. The methodof claim 20, wherein the integrated presentation package is configuredto be launched in at least one of a trading desktop, a mobileapplication and a spreadsheet application.